Service Tier Mapping¶
Service-design artifact — instantiates Acceptable Substitution Mapping
Defines a graded set of service bundles, each preserving the core outcome for a different segment's needs and budget, so a customer can be matched to an acceptable tier.
A Service Tier Mapping is an artifact that defines a graded ladder of service packages — good, better, best — where each tier is a deliberately different combination of attributes that still preserves the core outcome for the segment it targets. Its defining move is that the tiers are not interchangeable equals: a higher tier is not the "same as" a lower one, and a lower tier is not a certified substitute for a higher one. Instead, each rung is calibrated to a different acceptable level of need, so a customer with modest requirements gets a leaner package that is genuinely acceptable for them, while a demanding customer gets a richer one. The artifact's job is to make acceptable variation productized and legitimate — a customer is matched to (or moved along) a band of acceptability — rather than negotiating a bespoke deal each time or being forced into one-size-fits-all.
Example¶
A managed-IT services firm supports business clients and cannot offer every client a dedicated engineer, but must still guarantee that every client's core outcome — incidents get resolved — holds. It builds a service tier mapping with three rungs. Bronze: business-hours support, four-hour response on critical issues, shared help-desk queue — acceptable for a small shop whose systems can wait overnight. Silver: extended hours, one-hour critical response, a named account contact — for a mid-size firm that loses real money to downtime. Gold: 24/7 coverage, fifteen-minute response, a dedicated engineer and quarterly reviews — for clients whose operations never stop. Each tier is a real, self-consistent package sized to a segment; the floor tier, Bronze, still clears the non-negotiable ("critical incidents are resolved, not abandoned"), just more slowly. A named product owner maintains the definitions and pricing and reviews them as costs and client needs shift. When a client's needs straddle two rungs — a small firm with one mission-critical system — an exception path lets them assemble a custom bundle rather than being forced up an entire tier. The map turns "what can we offer at different price points without dropping the ball" into an explicit, owned ladder.
How it works¶
What makes this the mechanism, rather than a price list, is that each tier is engineered to preserve the outcome at a different acceptable level, with ownership and an escape hatch:
- Rungs, not equals. The tiers form a graded band of acceptability; each meets a different level of need, so they are ordered, not interchangeable.
- The floor still clears the non-negotiable. Even the leanest tier must preserve the core outcome; a rung that dips below it is a downgrade masquerading as an option, not a legitimate tier.
- Someone owns the ladder. A named owner maintains the tier definitions and their pricing and revises them as costs, competition, and segment needs change.
- A straddle has a path. Customers whose needs fall between rungs can invoke an exception to assemble a custom bundle, so the ladder bends instead of forcing a bad fit.
Tuning parameters¶
- Number of tiers — how many rungs the ladder has. More tiers fit needs precisely but proliferate into a confusing menu and dilute each tier's meaning; fewer are clear but coarse.
- Spread between tiers — how far apart adjacent rungs sit. Wide spreads make the choice obvious but leave gaps that strand in-between customers; narrow spreads fit better but blur why anyone should climb.
- Floor placement — where the lowest tier sits relative to the minimum acceptable outcome. Set with margin, the floor is safe but may over-serve the frugal; set too low, it quietly breaches the non-negotiable.
- Customization latitude — how freely the exception path allows off-ladder bundles. Generous latitude fits edge cases but erodes the clarity and economics of standard tiers; tight latitude keeps the ladder crisp but forces poor fits.
- Re-tiering cadence — how often the owner revisits the definitions. Frequent revision tracks shifting needs and costs; rare revision lets the ladder drift out of step with what segments actually require.
When it helps, and when it misleads¶
Its strength is matching a varied population to acceptable offerings without bespoke negotiation: it makes "acceptable for you" explicit and self-serve, and it lets a provider serve budget-constrained and demanding customers from one coherent structure — the good-better-best[n1] logic of productized service levels.
Its signature failure is a floor tier that dips below the real minimum: pressure to hit a low price point shaves the cheapest rung until it no longer preserves the core outcome, so the "entry tier" is a disguised downgrade. Tiers can also proliferate until the ladder confuses more than it clarifies, and a mapping can be used manipulatively — anchoring or upselling by making a middle tier look mandatory. The classic misuse is presenting a lower tier as "equivalent" to a higher one to close a sale, when it has actually dropped a load-bearing attribute. The discipline is that the floor tier must always clear the non-negotiable outcome, the owner must review the ladder against real segment needs, and the differences between tiers must be stated honestly rather than blurred to drive upgrades.
How it implements the components¶
The mapping realizes the graded-offering slice of the archetype — it structures acceptable variation into owned tiers, and neither certifies equals nor draws trade curves:
tiered_acceptability_band— the ladder of rungs is the tiered band: each tier a distinct, acceptable level of the outcome for a different segment.exception_and_appeal_path— the custom-bundle route handles customers whose needs straddle tiers, so the ladder accommodates edge cases without breaking its structure.substitution_owner— a named owner maintains the tier definitions and pricing and is accountable for keeping the floor honest.
It does not certify one-for-one interchangeable equals with an evidence_or_validation_criterion — its tiers meet deliberately different levels, not the same requirement — which is the Equivalency Table, its nearest artifact twin, holder of the acceptable_bundle_set of true equivalents. Nor does it plot a substitution_rate_or_exchange_ratio between attributes; that is the Design Tradeoff Curve.
Related¶
- Instantiates: Acceptable Substitution Mapping — it turns "what can we acceptably offer at different levels" into an owned, graded ladder of bundles.
- Consumes: Conjoint or Tradeoff Survey — measured willingness-to-trade tells the owner where to draw the rungs and what each segment will accept.
- Sibling mechanisms: Equivalency Table · Design Tradeoff Curve · Indifference Map · Approved Alternative Catalog · Conjoint or Tradeoff Survey · Preference Elicitation Workshop · Procurement Equivalence Review · Substitution Matrix · Exception Review Workflow
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Service Tier Mapping operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it defines a graded set of service bundles, each preserving the core outcome for a different segment's needs and budget, so a customer can be matched to an acceptable tier.
Independent corroboration: The frozen evidence defines Service Tier Mapping as 'Defines a graded set of service bundles, each preserving the core outcome for a different segment's needs and budget, so a customer can be matched to an acceptable tier', so its operative form is Representation, Specification & Plan.
Nearest alternative: Decision, Gate & Allocation — Service Tier Mapping includes features of a case-specific gate, selection, routing, prioritization, or resource disposition, but its defining operation is a static representation, map, specification, schema, or prospective plan that externalizes information.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Matching heterogeneous needs and willingness to pay to differentiated bundles is market segmentation and versioning economics.
Related originating lineages:
- Operations Research — Constrained matching assigns segments to feasible bundles under capacity and budget limits.
- Organizational & Management Science — Portfolio design ensures each tier preserves the core outcome and can be delivered.
- Public Administration & Policy — Tiering in public services must preserve equitable minimum access despite different needs.
Review resolution: The blind reviewers agree that economics_finance is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, domain reach disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined record shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance, and encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Good-better-best is a product-line strategy that offers a tiered ladder of versions at rising price and capability, letting a single provider serve segments with different willingness to pay while anchoring the middle option. Service tier mapping applies the pattern to services, with the added discipline that even the "good" tier must preserve the core outcome. ↩