SIDM · PART III
Chapter 9 — Applying the SIDM Brand Maturity Model
The SIDM brand maturity model organizes assessment into five dimensions and determines maturity through three levels . The assessor must first define the…
The SIDM brand maturity model organizes assessment into five dimensions and determines maturity through three levels. The assessor must first define the object and point in time, gather evidence, establish a level for each dimension independently, and specify improvement actions. The model identifies the condition and development direction of brand-oriented equipment design; it does not calculate a simple average score, nor does it convert the three design philosophies into a scoring system.
Project Assessment and Enterprise-Level Brand Maturity
A project assessment addresses the current concept, equipment, physical product, or phase deliverable. It asks whether a design characteristic has been established, whether intent has been realized, and which conditions for a particular level are supported. A concept can validate expression direction and feasibility assumptions; it cannot establish physical quality or long-term experience. One successful delivery cannot, on its own, establish that the enterprise has reached the Brand Equity level.
Enterprise-level assessment combines evidence from different products, projects, deliveries, customer and user feedback, product-system development, internal rules, and sustained business experience. Confirmation of the highest level, in particular, is primarily an enterprise-level judgment. Individual projects contribute evidence, while an enterprise's past competence never exempts a new project from verification.
Brand recognition, quality expression, and interaction experience can initially be assessed on a single machine, but higher-level conclusions require comparison across equipment and deliveries. Product family development is inherently concerned with models, product families, or multiple projects. Business value requires evidence from the enterprise's products, customers, and commercial processes.
| Dimension | Primary object | Scope to record |
|---|---|---|
| Brand Recognition | Equipment, product families, customer perception | Products, settings, and customer contact |
| Quality Expression | Physical units, production batches, deliveries | Batches, sites, and operating conditions |
| Interaction Experience | Touchpoints, tasks, and users | People, tasks, exceptions, and site conditions |
| Product Family Development | Product families and the enterprise product system | Model differences, applicability of rules, and reuse |
| Business Value | Enterprise, customer relationships, business processes | Customer types, comparison conditions, and observation period |
The Formal Five-Dimension, Three-Level Framework
| Dimension | Level 1: Foundational Expression | Level 2: System-Building | Level 3: Brand Equity |
|---|---|---|---|
| Brand Recognition | Identification through explicit brand marks | Recognition through product language | Recognition through brand DNA |
| Quality Expression | Basic manufacturing presentation | Systematic quality development | Shared confidence in brand quality |
| Interaction Experience | Basic touchpoint usability | Coherent system interaction | Established brand experience expectations |
| Product Family Development | Basic individual-product presentation | Consistent product-family language | Product-system assets; no fixed minimum number of formal series |
| Business Value | Monetization of functional specifications, supported by actual sale and corresponding fulfillment evidence | Competitive trust advantage | Compounding returns from brand equity |
Level 1 asks whether a qualifying result exists. Level 2 asks whether a repeatable system exists. Level 3 asks whether an asset exists. Results must satisfy the necessary conditions of their own dimension. System-building requires explicit rules and verified repeated execution. Brand Equity requires recurrence, continuity, and demonstrated benefit to future products or decisions. Chapters 11–15 give the dimension-specific conditions.
For Business Value, Level 1 requires evidence of both a completed transaction and corresponding fulfillment. If only a purchaser's comparison or procurement review is documented, record: “Transactional foundations established; monetization outcome pending verification.” Do not confirm monetization of functional specifications.
Five Categories of Assessment Evidence
| Evidence category | Typical materials | Limits of interpretation |
|---|---|---|
| Outcome evidence | Physical-product photographs, on-site condition, task-completion records | Images do not replace undisplayed touchpoints or actual user behavior |
| Rule evidence | Product-language principles, CMF specifications, quality standards, interaction rules, checklists | A document's existence is not evidence of implementation |
| Execution evidence | Application and deviation management across equipment, batches, and projects | Identify precisely which rules were reused and where |
| External evidence | Customer/user feedback, procurement reasoning, market recognition, recommendations | Record the respondent, context, and actual contact with equipment |
| Business evidence | Transaction and fulfillment records, communication, selection, price support, case reuse, continuing cooperation | Isolate the observable contribution of design without omitting other influences |
Each material piece of evidence should identify its source, date, object, applicable range, and retrievable location. Evidence may support multiple dimensions, but conclusions must remain separate. For example, assembly records may demonstrate consistent physical quality and also show reuse of a product-family rule. Each assessment must explain what the record proves for its own dimension; “we have a standard” is not sufficient.
Rule-Based Conditions for Level 2
System-Building ordinarily requires outcomes, rules, and repeated execution together. Good results stored only as an individual's tacit experience do not establish a system. Similarly, rules that exist as documents but have not been executed on real products or projects do not establish Level 2. A rule must identify applicability, permitted variation, and critical verification conditions; repeated execution must identify actual objects and records.
Several independent, traceable execution objects within one project may demonstrate repetition, but their representativeness must still be assessed before making enterprise-wide claims. Multiple photographs of one machine or repeated presentations of one delivery do not constitute multiple successful deliveries. Where rules are undergoing first-project validation, record “foundation for System-Building established” and specify the next execution and confirmation needed.
The Three Gates to Level 3
Recurrence requires repeated performance across machines, projects, or deliveries, rather than a fortunate one-off result. Continuity requires verification over time, real use, or ongoing delivery, demonstrating that the result is not temporary. SIDM sets no arbitrary minimum number of years; the assessment must describe the tasks, changing conditions, and delivery range actually observed.
Asset value means that what was built earlier has started to help future work. Examples include product language guiding new equipment, established quality supporting customers' expectations, interaction rules reducing the burden of learning a new machine, a product system supporting subsequent communication, or past projects helping customers make future choices. Actual assistance must be documented. An assertion that material could be reused is not evidence that it has become an asset.
All three gates must be met. Level 3 ordinarily requires external evidence, not solely an enterprise's self-assessment. Reuse of internal rules must also be tested for its contribution to relevant customer perception, quality commitments, experience expectations, or product evolution. A particular dimension need not demonstrate every possible commercial outcome: each dimension establishes its own asset effect.
Highest Fully Satisfied Level
Each dimension is assigned the highest level whose necessary conditions are fully satisfied. Confirm the foundational conditions first, then the Level 2 outcome-rule-execution combination, and finally the three Level 3 gates with appropriate external evidence. Higher-level evidence cannot compensate for failure of a lower-level prerequisite. Existing market recognition does not excuse unreadable current brand identification; positive user comments cannot conceal an unusable critical task.
If Level 2 is supported but Level 3 is not, report “System-Building; evidence insufficient for Brand Equity.” Do not discard the established Level 2 conclusion. Partial higher-level evidence may be recorded as progress and a future verification priority, but not used to skip levels. Foundational deficiencies must be corrected before debating advanced maturity.
Three Auxiliary Assessment States
Below foundational conditions: the necessary conditions of Level 1 have not been met. Insufficient evidence: the capability may exist, but evidence does not support the proposed level; list available support, missing material, and collection actions. Not currently applicable: the particular judgment truly cannot apply to the assessed object; record why and delimit the scope. These are not a fourth maturity level.
A missing capability must not be relabeled “not applicable.” A first brand-oriented design project without cross-product repetition should record its current results and evidence gaps. Planning a product family without establishing rules should be described accurately, rather than exempted from evaluation. During a concept-only review, physical quality may be marked not yet verifiable at that phase; existing company products can still be evaluated separately for enterprise quality maturity.
Conflicting Evidence and Reassessment
When management self-assessment, interviews, presentations, and observed site behavior conflict, give appropriate priority to actual behavior, real equipment, real use, and sustained delivery. First check whether objects, dates, tasks, and versions match; then determine whether differences reflect sampling, execution deviation, or a failed rule. Do not average contradictory evidence or retain only comments that support the desired result.
Use the model at least at input diagnosis, physical delivery, and subsequent enterprise reassessment. Diagnosis establishes the starting condition and project objective; delivery checks project realization; reassessment checks repeated application, external expectations, and asset effects. Set reassessment dates according to product updates, usage tasks, and delivery rhythm, with explicit triggers and responsible roles.
Five-Dimension Maturity Profile and Action Plan
A complete assessment identifies the object, observation window, confirmed level of each dimension, five categories of evidence, critical gaps, intended improvements, priority actions, responsible roles, evidence to gather, and reassessment checkpoints. Present a five-dimension profile, preserving meaningful differences and their impact instead of reducing the enterprise to one score.
| Dimension | Confirmed condition | Key supporting evidence | Gap and next step |
|---|---|---|---|
| Brand Recognition | Highest fully satisfied level or auxiliary state | Relevant evidence identifiers and what they establish | Missing condition, action, responsibility |
| Quality Expression | As above | As above | As above |
| Interaction Experience | As above | As above | As above |
| Product Family Development | As above | As above | As above |
| Business Value | Level 1 only when both sale and fulfillment are evidenced | Transaction, fulfillment, and design-contribution evidence | Procurement comparison only: transactional foundations established; monetization pending verification |
This is a reporting template, not an assessment of a specific enterprise. Actual conclusions require application of this chapter and the conditions in Chapters 11–15. Chapter 10 explains four ways to observe and collect supporting evidence.
Illustrative SIDM Maturity Assessment
The following example is fictional and represents neither EQPID nor any actual client. It describes an automation-equipment enterprise assessed across three models in one product family, four deliveries, and one subsequent iteration over 18 months. These numbers illustrate evidence collection, not a minimum number of products, deliveries, or months. Each dimension uses the highest fully satisfied level.
| Item | Illustrative judgment and follow-up |
|---|---|
| Available evidence | E1: physical products and four-perspective observations; E2: product language, quality, and interaction specifications; E3: repeated implementation and change records; E4: customer interviews and actual user tasks; E5: signed sales plus corresponding delivery/fulfillment records |
| Brand Recognition | System-Building. Recognizable features, expression rules, and repeated execution supported by E1–E4. Customers recognize the manufacturer but do not yet consistently associate its identity with core company values. Next: track recognition and value associations for new models |
| Quality Expression | System-Building. Physical quality is verified and standards are executed across four deliveries (E1–E3). Evidence of stable long-term customer expectations is missing. Next: obtain continued-use and follow-up purchasing feedback |
| Interaction Experience | System-Building. Task touchpoints and professional prerequisites are met; interaction rules recur across models (E1–E4). Evidence that users transfer learned experience is insufficient. Next: document learning, maintenance, and exception handling on new equipment |
| Product Family Development | Brand Equity. Earlier-level conditions are fulfilled; rules persist across subsequent models and iterations, justified changes reduce repetitive design, and customers understand product relationships (E1–E4). The third-level conditions are supported within the assessed scope. Next: test adaptation to a new setting |
| Business Value | Foundational Expression. Completed sales and corresponding fulfillment are documented (E5). Customers recognize equipment expression, but repeatable value-explanation rules and evidence for competitive trust advantage are insufficient. Next: track use of case material and customer selection reasons |
| Priority action | Project manager coordinates evidence collection; design and engineering leads test interaction rules; marketing and sales record customer understanding and procurement reasoning. Reassess new tasks and customer responses after three months; long-term claims still depend on real use and delivery evidence |
If E5 included only procurement comparisons, Business Value could not reach Level 1: report “Transactional foundations established; monetization outcome pending verification.” If the absence of any sale is verified, use Below foundational conditions. If sale or fulfillment status is unknown, use Insufficient evidence. Report dimensions independently, with no aggregate score.
KEEP READING





































