Skip to main content

Concept Model: What, Why and How

Difficulty:

How do we distill user scenarios into “concept”, and how do we comprehend “concept” and build models on it in the process of product design? It is very essential to complex business products. If we don’t distill correctly nor modelling the wrong way in the beginning, we must suffer from designing ill-used products, piling up tech debt, and bringing disaster into technical architecture. Furthermore, those consequences would drag down the whole product. Distilling concept is actually the same thing for UX designer, BA and architect. When they all share the same understanding in “concept”, and thus domain models come out simultaneously, and we can map the architectural design of application and technology well to business and user scenarios. This time sharing experience design, BA and technical personnel from the perspective of the team, using examples to illustrate how to collaborate to build a conceptual model to guide technical design.

  1. concept? domain?
  2. Why the conceptual model is fundamental
  3. Build a conceptual model
    1. From experience perspective: Refining "concepts" from user scenarios and opportunities, creating prototypes
    2. From demand perspective: from the prototype to enrich the "concept" elements and the relationship between the "concepts"
    3. From technical perspective: examine the concepts and their relationships from the perspective of the scheme, and provide feedback and optimization
    4. From collaborative perspective: constructing conceptual models and defining design principles
  4. Tips

Takeaway

Understand what a conceptual model is, its necessity, application scenarios, and general ideas and examples for constructing a conceptual model