Discovery workshop

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A discovery workshop is a collaborative session for investigating user needs, business problems, domain concepts, or solution possibilities.

A discovery workshop is a facilitated, collaborative session for building shared understanding of business domains, boundaries, terminology, processes, and complexity. It helps teams surface differing assumptions before changing products, architecture, or organization. section 17.1.1

Effective discovery workshops can:

• Define and refine domains and terminology, including time planning and payments. section 17.1.1
• Use collaborative modeling, such as EventStorming, to expose overlooked processes and competing team understandings. section 17.1.1
• Reveal organizational improvement opportunities involving coordination, dependencies, autonomy, and business-aligned teams. section 17.1.1

Payroll domain discovery

A payroll organization used domain discovery and modeling workshops to map company domains and reconsider team structure. The work addressed sensitive payroll data alongside data governance, consistency, and decentralized decision-making. section 17.1.1

Figure 17.1 Payroll period MindMap

Use the payroll-period mind map as a visual artifact for exploring domain processes and relationships. section 17.1.1

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes

Maps domains, boundaries, terminology, processes, and team interactions through collaborative modeling.

Examples

Uses time planning, payments, payroll periods, declarations, and sensitive payroll data as discovery subjects.

What you can do after

Apply via collaborative modeling to clarify domains, identify improvement opportunities, and guide business-aligned organizational change.

How it connects

Connects domain modeling, EventStorming, organizational structure, team autonomy, and data governance.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

Related concepts

• Example Mappingused by · Example Mapping is a collaborative technique that organizes user stories, rules, examples, and questions to clarify requirements and expected behavior.
• demonstrationproduces · A demonstration is an example pairing an input, request, or prompt with a corresponding output, answer, or label to illustrate a task or expected behavior.
• shared understandingproduces · Shared understanding is a common interpretation among people of relevant information, context, assumptions, expectations, goals, or decisions.
• software design EventStormingused by · Software design EventStorming is a collaborative modeling technique that explores domain events and processes to inform software structure and behavior.
• user storyuses · A user story is a concise requirement describing a desired software capability, interaction, or outcome from a user’s or stakeholder’s perspective.
• structured conversationhas part · A structured conversation is a deliberately guided discussion that uses questions or an organized sequence to clarify intent, requirements, or expected behavior.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.