Reference

Worked example: Norvane Industrial Supply, margin leakage interview programme

Part of the Primary Research Synthesis skill · loaded on demand from SKILL.md

This is one complete pass through the skill, from mandate to synthesis. The client and all interviewees are synthetic; the numbers are internally consistent and are the ones referred to in SKILL.md. Read it when you want to see what a finished coded excerpt, saturation log, theme hierarchy, insight statement and gap table actually look like before you produce your own.

Contents

  1. Situation and mandate
  2. Research design
  3. Interview guide (extract)
  4. Open coding: ten coded excerpts
  5. Memo written during coding
  6. Saturation log
  7. Codebook after consolidation
  8. Axial coding: the paradigm applied to the lead theme
  9. Theme hierarchy with evidence counts
  10. Selective coding: the core category
  11. Espoused theory vs theory-in-use
  12. Insight statements
  13. Negative case and what it changed
  14. What went to the client, and hand-offs

1. Situation and mandate

Norvane Industrial Supply is a mid-market distributor of maintenance, repair and operations products (fasteners, tooling, safety equipment, fluids) with revenue of EUR 640 million, 38 branches in four regions, and about 310 field sales representatives. Gross margin has fallen from 27.1 percent three years ago to 25.6 percent and then 24.9 percent last year. Each margin point is worth roughly EUR 6.4 million of gross profit.

Eighteen months ago the company launched a Price Discipline Programme. Its two visible mechanisms are a list-price-based quoting tool and a discount authority matrix: representatives may discount up to 8 percent off list on their own authority, branch managers up to 15 percent, and anything above 15 percent requires a regional director. A pricing playbook was issued and a webinar delivered.

The CEO's mandate: "The programme should have put two points back by now. Realised margin has not moved. I want to know what is actually happening in the branches, not what the pricing team's dashboard says."

The problem statement came through problem-framing and the lead hypothesis through hypothesis-stress-testing: that the matrix thresholds are set too high. The research was asked to test that and to surface whatever else was driving leakage.

2. Research design

ElementDecisionReason
SegmentsSales reps (8), branch managers (6), regional directors (3), pricing team (2), customer procurement leads (3): 22 interviewsEvery level of the approval chain, the system owners, and the counterparty who sees behaviour from outside
Site spreadBranches chosen across all four regions, including two where margin held up and three where it fell mostDeviant cases are where the mechanism shows itself
ObservationFour half-day branch visits: two ride-alongs with reps, two desk-side sessions watching quotes being built and escalatedInterviews give espoused theory; observation gives theory-in-use
System dataTwelve months of quote log (61,400 quotes); a random sample of 200 invoices checked for non-price concessions; CRM rate-card status for all active accountsTriangulation for every claim that can be counted
Format45 to 60 minutes, semi-structured, two consultants (one asking, one noting), recorded with consent, transcribed within 24 hoursCoding starts the day after each interview
Sequencing14 interviews fixed with the client up front; 8 held back and allocated after the first coding passTheoretical sampling within a client-agreed list
Stop rule (set in advance)For each segment: three consecutive interviews with no new codes and no new properties on the top three themes; minimum six interviews per segment before saturation may be claimedWritten down before fieldwork so it cannot be adjusted to fit the calendar

3. Interview guide (extract)

The guide pairs every policy question with an incident question on the same topic, so that espoused and in-use data are collected side by side.

Section 2: Discounting in practice (20 minutes)

2.1  How does discount approval work in your branch?              [espoused]
2.2  Tell me about the last quote you escalated. What was the
     order, what did you ask for, what happened, how long did
     it take?                                                       [in-use]
2.3  When did you last have an escalation declined? What happened
     to the order?                                                  [in-use]
2.4  What does the company say it sells on?                        [espoused]
2.5  In that last escalated quote, at what point in the
     conversation did service come up, if at all?                   [in-use]
2.6  Beyond the percentage, what else do you sometimes give a
     customer to close? (probe: freight, terms, samples, returns)  [in-use]

4. Open coding: ten coded excerpts

Each excerpt is verbatim (fillers removed), attributed by role, region and interview number, and coded line by line. Codes are tagged E (espoused) or U (in-use) where the distinction applies.

Excerpt 1. Sales representative, Region North, interview 01. "Officially I have got 8 percent. But if I lose a 40,000 euro order over two points, my manager is going to ask me why I did not call him. So I call him. He always says yes."

SegmentOpen codeTag
"Officially I have got 8 percent"authority-limit-knownE
"if I lose ... my manager is going to ask me why I did not call"fear-of-attributable-lossU
"So I call him"pre-emptive-escalationU
"He always says yes"approval-as-formalityU

Excerpt 2. Branch manager, Region West, interview 03. "The matrix is fine on paper. My bonus is on branch revenue and gross margin euros, not margin percent. A 12 percent discount on a big order still adds margin euros, so why would I say no?"

SegmentOpen codeTag
"The matrix is fine on paper"policy-endorsed-verballyE
"My bonus is on ... gross margin euros, not margin percent"bonus-on-margin-eurosU
"A 12 percent discount on a big order still adds margin euros"volume-beats-rateU
"why would I say no"manager-has-no-reason-to-declineU

Excerpt 3. Regional director, Region East, interview 05. "I approve maybe 30 escalations a week. I would say I decline two. If I declined more, the reps would stop bringing me the big ones and quote inside their limit, then pad the freight-free threshold or throw in samples."

SegmentOpen codeTag
"30 escalations a week ... decline two"approval-rate-near-totalU
"reps would stop bringing me the big ones"escalation-as-visibility-toolU
"pad the freight-free threshold or throw in samples"off-system-concession-workaroundU

Excerpt 4. Pricing analyst, head office, interview 06. "The tool logs the discount at quote. It does not log free delivery, extended payment terms, or the sample units. Realised margin runs about 1.8 points below quoted margin and nobody owns that gap."

SegmentOpen codeTag
"logs the discount at quote"system-captures-price-onlyU
"does not log free delivery, extended payment terms, or the sample units"unlogged-concessionsU
"1.8 points below quoted margin"quoted-vs-realised-gapU
"nobody owns that gap"leakage-has-no-ownerU

Excerpt 5. Sales representative, Region South, interview 07. "Customers know the list is a fiction. The buyer at one of my top accounts keeps our last three invoices in his drawer. You cannot start at list with him. You start at last invoice minus something."

SegmentOpen codeTag
"Customers know the list is a fiction"list-price-not-credibleU
"keeps our last three invoices in his drawer"customer-anchors-on-historyU
"start at last invoice minus something"negotiation-starts-below-listU

Excerpt 6. Procurement lead, customer (industrial manufacturer), interview 09. "Norvane reps are the easiest on our panel to negotiate with. Your competitor's reps come with a price and a reason. Norvane reps come with a price and a pen."

SegmentOpen codeTag
"easiest on our panel to negotiate with"rep-concedes-early (external view)U
"a price and a reason"competitor-holds-price-with-rationaleU
"a price and a pen" (in-vivo)no-value-narrative-in-negotiationU

Excerpt 7. Branch manager, Region East, interview 08. "I read the playbook once. Honestly we did not train on it. There was a webinar. Most of my team were on the road that afternoon."

SegmentOpen codeTag
"I read the playbook once"playbook-read-not-usedU
"we did not train on it ... a webinar"training-nominalU
"Most of my team were on the road"rollout-missed-field-staffU

Excerpt 8. Observation note, ride-along with sales representative, Region North, visit 2 (same rep as interview 01). Rep prepared a quote at 8 percent discount before phoning the customer. Customer asked for 10 percent. Rep said "let me check", sent a text to the branch manager, received "ok 12" four minutes later, and confirmed 12 percent. Service levels were not mentioned during the call. Afterwards the rep said, "That is a good outcome, we kept the order."

SegmentOpen codeTag
quote prepared at 8 percent before contactpre-emptive-discountingU
text to manager, reply in four minutesapproval-latency-minutesU
approved above the amount requestedapproval-exceeds-requestU
service not mentionedvalue-story-absent-from-negotiationU
"we kept the order"success-defined-as-not-losingU

Excerpt 9. Regional director, Region West, interview 12. "We sell on service. That is genuinely true, our fill rate is 97 percent and nobody else in the region is close. But the reps do not know how to say that inside a price conversation, so they give the discount first and talk about service afterwards."

SegmentOpen codeTag
"We sell on service. That is genuinely true"value-proposition-espousedE
"fill rate is 97 percent"service-advantage-realU
"give the discount first and talk about service afterwards"service-as-post-hocU

Excerpt 10. Sales representative, Region West, interview 10. "About half my accounts have a legacy rate from before the programme. Nobody told us whether those reset. So I left them alone. If I had reset them I would have lost accounts and been asked about it."

SegmentOpen codeTag
"legacy rate from before the programme"legacy-pricing-untouchedU
"Nobody told us whether those reset"policy-ambiguity-on-legacyU
"lost accounts and been asked about it"fear-of-attributable-lossU

Note how fear-of-attributable-loss appears in excerpts 1 and 10 from different reps in different regions on different topics (escalation and legacy rates). That repeated appearance across contexts is the first sign it may be more than a code.

5. Memo written during coding

Written after interview 08, before the second coding pass:

Three things now point the same way. Reps escalate before being asked (01, obs 2), managers approve at a rate that makes the approval meaningless (03, 05), and the director says he will not decline more because reps would route around him (05). The matrix is being used as a way to share responsibility for a discount, not to decide whether to give it. The question I do not yet have data on: is there any branch where declines are normal, and if so what is different there? Allocate two held-back interviews to Branch South-1 (margin up 0.9 points last year) and its regional director.

6. Saturation log

New open codes per interview, in the order conducted. Segment codes: R rep, BM branch manager, RD regional director, P pricing, C customer.

IntSegNew codesCumulativeNew properties on top 3 themes?
01R1414n/a
02R923n/a
03BM831yes
04R536yes
05RD642yes (routing around declines)
06P446yes (unlogged concessions quantified)
07R349yes
08BM251no
09C455yes (external view of posture)
10R156yes (legacy rates)
11BM157no
12RD057yes (service as post-hoc)
13C158no
14R058no
15BM058yes (negative case, South-1)
16P058no
17R058no
18BM058no
19RD058no
20C058no
21R058no
22BM058no

Reading: code saturation arrived at interview 13 (no new codes thereafter). Meaning saturation on the top three themes arrived at interview 15, when the negative case added a new condition. Against the stop rule as written, only the rep segment met it in full: interviews 14, 17 and 21 added neither codes nor properties. Branch managers ended one interview short, because the South-1 case at interview 15 reset the count and only 18 and 22 followed; the write-up reports that segment as "consistent across six, with the stop rule met on codes but one interview short on properties" and names the one condition (lost-order review) that a seventh manager could still vary. Directors, pricing and customers are below the six-interview minimum, so their findings are stated as "consistent across the n interviewed" rather than "saturated". The partner accepted the seven consecutive interviews with nothing new across all segments (16 to 22) as grounds to stop, and the method appendix says so in those words rather than claiming saturation the log does not show.

7. Codebook after consolidation

Fifty-eight open codes were consolidated to 24 in the second pass. Extract of the codebook entry format:

CodeDefinitionIncludeExcludeExampleTag
pre-emptive-escalationRep seeks approval above own authority before the customer has asked for itPhone, text or system request made before or during quote preparationEscalation after a customer counter-offer (code as reactive-escalation)"So I call him" (01)U
approval-as-formalityApprover grants without testing the case; rate near 100 percent or decision in minutesStatements by approver or requester; observed decisions under 15 minutesApprovals with documented pushback"He always says yes" (01); "ok 12" in 4 min (obs 2)U
fear-of-attributable-lossActor anticipates being personally questioned for a lost order or accountAny level; any topicGeneral risk aversion not tied to being asked"asked me why I did not call" (01); "been asked about it" (10)U
off-system-concessionValue given to a customer that is not captured in the quote toolFreight waiver, extended terms, samples, returns toleranceDiscount percentage itself"pad the freight-free threshold" (05)U
value-story-absentService advantage not used inside the price negotiationRep, manager or customer accounts; observationCases where service is cited before a price is given"a price and a pen" (09)U

8. Axial coding: the paradigm applied to the lead theme

Theme A, "the approval matrix routes discounts instead of deciding them", reassembled with the Strauss and Corbin paradigm:

Paradigm elementContentEvidence
PhenomenonDiscounts above rep authority are approved almost without exception, quickly, and often above the amount requestedQuote log: 4,120 escalations in 12 months, 91 percent approved, median 11 minutes; obs 2 and 4
Causal conditionsReps face large orders with thin authority; a declined escalation followed by a lost order is personally attributable to the rep or the approverInt 01, 04, 07, 10, 14
ContextBranch and manager bonuses paid on revenue and gross margin euros, so any positive-margin order improves the bonusInt 03, 08, 11, 15, 18
Intervening conditionsDirectors know that declining drives reps to off-system concessions, so they decline rarely to keep escalations visibleInt 05, 12
StrategiesReps escalate pre-emptively; managers approve by text; directors approve to preserve visibilityInt 01, 03, 05; obs 2, 4
ConsequencesThe matrix shifts the discount decision upward without changing the decision rule; discount depth is unchanged; the audit trail shows complianceQuote log; pricing team's own dashboard shows 100 percent "within authority"

9. Theme hierarchy with evidence counts

Counts are the number of interviews in which the theme appears, out of 22, with the segment split (R 8, BM 6, RD 3, P 2, C 3). Intensity is rated high if raised unprompted and with emphasis by most of those who mentioned it. Triangulation lists non-interview sources.

ThemeInterviewsRBMRDPCIntensityTriangulation
A. Matrix routes rather than decides16/2285300HighQuote log (91 percent approval, median 11 min); obs 2, 4
B. Bonus rewards margin euros, so volume beats rate11/2236200High among BMsBonus plan document
C. Leakage is off-system in non-price concessions13/2263121MediumInvoice sample: freight waived on 31 percent, extended terms on 12 percent, samples on 6 percent; quoted-to-realised gap 1.8 points
D. No value narrative inside the negotiation12/2243203High among customersObs 1 to 4: service raised before price in 0 of 7 observed negotiations
E. List price is not credible; legacy rates anchor14/2274012MediumCRM: 44 percent of active accounts on pre-programme rate cards
Counter: matrix is working2/2200020LowPricing dashboard (measures logged compliance only)

Reading the segment split: theme B is a manager theme (6 of 6) that reps rarely raise (3 of 8) because reps do not see the bonus mechanics; theme D is loudest from customers (3 of 3), which is the segment best placed to judge it. Neither theme should be discounted for low frequency in segments that cannot observe it.

10. Selective coding: the core category

Candidate cores were tested against the rule that a core must appear frequently, connect to most other categories, and explain variation (including the negative case).

  • "Incentive misalignment" (theme B): connects to A and partly to E; does not explain C or D; does not explain the South-1 negative case (same bonus, different behaviour). Rejected as core; retained as a major category.
  • "Weak execution of the programme" (theme with training and legacy ambiguity): describes symptoms; does not explain why approvers approve. Rejected.
  • "Not losing the order": appears in 17 of 22 interviews under several codes (fear-of-attributable-loss, success-defined-as-not-losing, manager-has-no-reason-to-decline, escalation-as-visibility-tool); connects to A (escalation shares the blame), B (bonus makes losing costly and approving free), C (concessions are the way to not lose when the percentage is capped), D (service talk is deferred because the discount is the reliable way to not lose), E (legacy rates are left because resetting risks a loss). Explains the negative case (section 13). Accepted.

Storyline: At Norvane, every discount decision at every level is governed by avoiding an attributable lost order. The Price Discipline Programme did not change that governing value; it gave people a procedure for sharing the responsibility for a discount. The matrix is therefore experienced as a routing system, the bonus makes approval costless, the quoting tool captures only the part of the concession that the procedure covers, and the service advantage is never spent in the negotiation because the discount is the surer way not to lose.

11. Espoused theory vs theory-in-use

TopicEspoused theory (what policy and leadership say)Theory-in-use (what the evidence shows people do)EvidenceGap typeGoverning variable sustaining it
Discount authorityReps may give up to 8 percent; higher discounts are tested by a manager or directorReps pre-clear discounts by text; 91 percent of 4,120 escalations approved, median 11 minutes; approvals often exceed the requestInt 01, 03, 05; quote log; obs 2, 4Known and toleratedWin, do not lose (the order)
What the company sells on"We sell on service, not price"Service is mentioned after the discount is agreed, or not at all; 0 of 7 observed negotiations led with serviceInt 09, 12; obs 1 to 4Unaware at leadership level; known at rep levelEmphasise rationality (service is "true", so it need not be argued)
Scope of pricing controlThe quoting tool governs the price the customer receivesFreight, terms and samples are given outside the tool; realised margin is 1.8 points below quotedInt 05, 06; invoice sampleKnown and concealed at branch level; unaware at head officeAchieve the purpose as I define it (close the order)
IncentivesThe bonus rewards margin disciplineBonus is paid on margin euros; any positive-margin order improves it regardless of discount depthInt 03, 08, 11; bonus planKnown and toleratedWin, do not lose
Programme rolloutEvery branch was trained on the playbookOne webinar; field staff largely absent; playbook read once by managersInt 08, 11, 18Unaware at head officeSuppress negative feelings (nobody reported that the webinar failed)
Legacy pricingProgramme applies to all accounts44 percent of active accounts on pre-programme rate cards; reps left them because resetting risks an attributable lossInt 10, 17; CRMPolicy is ambiguousWin, do not lose

The largest gaps sit on the topics the client most needed to understand, which is what the Model I analysis predicts: the organisation protects itself most where it has most to lose.

12. Insight statements

Each statement is written so that a reader can see the claim, the count behind it, its strength, and what would contradict it.

Insight 1. The discount authority matrix does not constrain discounts; it distributes responsibility for them. Evidence: 16 of 22 interviews (all 8 reps, 5 of 6 managers, all 3 directors); quote log shows 91 percent of 4,120 escalations approved with a median decision time of 11 minutes; 2 of 4 observations saw approvals above the amount requested. Counter-evidence: the pricing team (2 of 22) reads the same log as proof of compliance. Would be overturned by: a sample of declined escalations showing substantive review, which we did not find.

Insight 2. Margin leakage is larger than the quote log shows because roughly 1.8 points are given off-system in freight, terms and samples. Evidence: 13 of 22 interviews; invoice sample of 200 shows freight waived on 31 percent, extended terms on 12 percent, sample units on 6 percent. Strength: high on existence, medium on magnitude (pricing analyst's estimate, confirmed by a single sample).

Insight 3. Reps do not use Norvane's service advantage inside the price negotiation, so price is the only lever they pull. Evidence: 12 of 22 interviews including all 3 customers; 0 of 7 observed negotiations opened with service. Counter-evidence: none found; two directors believe reps do use it, but neither could cite an instance.

Insight 4. The behaviour at every level is governed by avoiding an attributable lost order, and the programme's mechanisms have been absorbed into that logic rather than changing it. Evidence: 17 of 22 interviews; explains themes A to E and the negative case. This is the governing insight and is stated with high confidence because it survived the negative-case test.

Insight 5. Where a manager makes lost orders discussable rather than attributable, discipline holds without any change to the matrix or the bonus (see section 13). Evidence: one branch, two interviews, one observation. Strength: low on prevalence, high on diagnostic value. This is a lead for strategic-choice and execution-planning, not a proven lever.

13. Negative case and what it changed

Branch South-1 was sampled deliberately because its margin rose 0.9 points while the company's fell. Its manager (interview 15) has the same bonus plan and the same matrix, and declines about 40 percent of escalations. What differs: he runs a fifteen-minute "lost orders review" every Monday in which every lost order of the previous week is discussed as a branch event, with the reason recorded and no individual blamed. His reps (interviews 17 and 21) described losing an order as "something we talk about on Monday" rather than "something I get asked about".

This case did two things to the synthesis. It killed "incentive misalignment" as the core category, because the incentive was identical and the behaviour was not. And it confirmed "not losing the order" as the core, because the branch that changed the social cost of losing was the branch where the matrix started to work. Without theoretical sampling toward a deviant case, the synthesis would have recommended a bonus redesign and left the mechanism untouched.

14. What went to the client, and hand-offs

The synthesis pack contained: the one-page governing insight; the five insight statements with counts; the theme hierarchy table; the espoused/in-use table; the saturation log as an appendix; twenty-two anonymised quotes attributed by role and region, each traceable to a transcript line in the working files; and the negative case as a separate page.

Hand-offs: the lead hypothesis from hypothesis-stress-testing ("thresholds too high") was reported as not supported, with the matrix at 91 percent approval regardless of threshold. The governing insight and the South-1 lead went to strategic-choice. The 1.8-point off-system leakage went to value-driver-modeling for sizing. The pack itself went to executive-communication for the storyline.