Step 02 / ADVANCED PLUS

Turn a proven idea into a dependable application.

Take an accepted proof into production through coached build cycles. Practise product thinking: stay close to users, build with IT, test the experience and own the service after release.

What the work can look like

Otto’s workshop invitations and reminders make the idea tangible: start with the recipient’s need, then connect the work, test the experience and keep improving the service.

Inside ADVANCED PLUS: how the work unfolds

Inside ADVANCED PLUS

How the
work unfolds.

  1. Scope

    Agree the users, value, boundaries and acceptance criteria.

  2. Build

    Create bounded slices with the right architecture and explicit human decisions.

  3. Verify

    Test representative cases, user acceptance, security and failure behaviour.

  4. Transfer

    Prepare release, monitoring, rollback, the runbook and an owned improvement backlog.

The intended outputs

What you take forward.

01

A managed application subject to agreed acceptance and release gates.

02

Evidence from technical checks and named human acceptance.

03

Ownership, release controls, a runbook and a change backlog.

ADVANCED PLUS / Product thinking in practice

From customer need
to a service people use.

Otto, TIP’s workshop automation, is a simple example. Invitations and reminders are the visible output. The product is the experience: people know what happens next, and the team can focus on the work.

A coaching illustration: follow an Otto-style service from a user’s need to an owned product. Select a stage to explore the work, the people and the evidence.

The user’s perspective

“I need to know when the session is, how to prepare and who can help if something changes.”

Illustrative user need

Start with the person receiving the email.

Talk to participants and the people coordinating workshops. Look at the questions they ask and where they have to chase. Define a useful outcome before choosing an automation.

Working togetherThe product owner brings the user need and prioritises the work. Users help test whether the problem is real.

Evidence to take forwardA short problem brief, a clear user and a way to recognise success.

Feedback returns to the beginning. Every release is another opportunity to understand the user and improve the service.

An operating model to explore

Think in products.
Organise around outcomes.

Our hypothesis is that more organisations may move towards a product-centred operating model: teams responsible for a continuing user outcome, with the capability to discover, build, run and improve a service.

That changes roles, responsibilities and decision rights. Knowledge workers can help bridge business and technology, working with IT to build useful services. In FUNCTION, leaders can test what that means for ownership, governance and the way their organisation operates.

Explore the operating model in FUNCTION →

How we used the method to build this site →

Read alongside the work / ADVANCED PLUS

Ideas to put into practice.

These are useful companions to the session. The practices carry forward as you apply them to real work.

More books for this session
The Culture Map ↗Erin Meyer

Notice cultural differences in communication, trust and decisions. Ask about the individual rather than assuming their preferences.

The Scrum Guide ↗ is a free companion for iterative delivery and review.

The next conversation

Build on what you learn.

The next step depends on the evidence and what the business needs.

Your next step

Discuss ADVANCED PLUS with Adam or Greg.

Bring the priority and the questions you need answered. Agree the scope and commitment before deciding.

Book a call