Learning / Collaboration

Workshops for Software and Product Projects

Turn meetings into decisions and artefacts.

A workshop should leave the team with something usable: a map, a prioritised question, a prototype, a decision or a next experiment. The sequence changes with the project. A redesign may begin with evidence; a new venture may need to test whether the problem is real.

Read the guide

At a glance

  1. Bring the people who can decide
  2. Choose exercises to answer live questions
  3. Leave with owners and next actions

01 / Frame the opportunity

We bring together the people who understand the audience, business goal and operational constraints. We map the current journey, what is known, what is assumed and what would count as progress. The output is a focused problem statement and a list of decisions that still need evidence.

For a physical or hybrid product, that map includes where the experience happens, who handles the handoff and which moments a screen cannot improve on its own.

02 / Explore people and possibilities

A user journey workshop traces what someone tries to do, where they hesitate and what success feels like. A concept session then compares a few ways to help. We deliberately separate evidence from preference, so a stakeholder's favourite feature does not silently become a user need.

Outputs can include a journey map, service blueprint, interface sketch, content outline or a small test plan. The right artefact is the one that helps the team choose what to try next.

03 / Shape the first release

We sort opportunities by value, risk and effort; identify technical dependencies; and select a release small enough to test. We also name the questions that must be answered before public launch, such as privacy, content ownership, accessibility and security.

The resulting scope can feed a delivery plan and agreement. It is a working hypothesis, not a promise that every idea raised in the room will be built.

04 / Review, launch and learn

During delivery, a review workshop uses a prototype or working build to resolve specific questions. Near launch, an operational walkthrough checks how the team will publish, support and measure the experience. After launch, we revisit what users actually did and decide what should change next.

Each workshop closes with the decision, its owner and the next checkpoint. That record is part of the product's memory, especially when a team changes later.

We select workshops to match the engagement. A short, well-prepared session can be more valuable than a full calendar of meetings.

External project website

Open this project site?

is hosted at . It will open in a new tab.