A Refinement Partnership, Not a Questionnaire

The Wikker Blueprint

We start by learning how your business really runs.

The Wikker Blueprint is the first step of every build. Over two to four weeks, a senior Wikker lead works with the owner and the people who do the work, and ends with a plan for the first release rather than a report.

What It Is Not

It is not a requirements document. Most software projects ask the client to write down, in technical and functional terms, everything the software must do, or bill for a discovery phase that does it for them. Requirements written that way tend to describe the software a business thinks it wants, and they lose what the people at the desk know. The Blueprint works the other way. We interview the owners and the people who do the work, read the records the process already produces, and write a business optimization proposal: what to change in how the work is done, and the software that would carry it.

What It Asks of the Business

The owner's time at the start and at the playback, and an hour or so from each person interviewed. Read access to the records that run the process: spreadsheets, exports from the systems in place, email metadata where it shows how work moves. We read records, not people's screens.

The Four Steps

  1. Listen

    Interviews with the owner, the managers and the people who carry out the process, and time spent watching the work where it happens. Wikker's lead asks; your people explain how the work really runs.

  2. Read the Data

    The spreadsheets that run each process, the audit trails, the email record of hand-offs, the exports from accounting and customer systems. This is where time and money are found to go.

  3. Synthesise

    Each finding is written down and traced to the interview or record behind it. The senior lead decides what matters and what is noise.

  4. Play Back

    The senior lead presents the findings to the owner and managers, in person or by video, ranked by what each would change, what software would carry it, and what it is worth. The first item becomes Release 1.

What the Blueprint Delivers

  • The optimized process, step by step, in the words the business uses.
  • A ranked plan of what to change, and the software that would carry each change.
  • The Release 1 backlog, ready to price.
  • The result Release 1 should deliver, and how it will be measured.

Who Does the Work

A senior Wikker lead runs the Blueprint from the first interview to the playback, and stays to lead the releases that follow. The person who hears how the work is done is the person who decides how the software should carry it. The findings are reviewed independently before the playback, so the plan the owner sees has been checked by someone who did not write it.

After the Playback

The playback ends with three choices, each the owner's: go ahead with Release 1 at the price set in the plan, act on the Blueprint another way, or stop. If Release 1 goes ahead, the fee is credited against it and work starts on the date in the plan. The ranked plan moves onto the Release Desk, and before each release the owner re-ranks what remains.

Fee and Length

Fee
From C$12,000, fixed in the proposal
Length
Two to four weeks
Credit
Credited against the first release

From C$12,000, fixed in the proposal before work starts. Two to four weeks, depending on how many processes and people are involved. The proposal states the fee, the processes in scope, the people to be interviewed and the date of the playback. The fee is credited against the first release. It is invoiced as a separate line.

When a Blueprint Fits

  1. A business of up to 500 people.
  2. Work that runs on spreadsheets and email.
  3. One person who holds a process together, and a business that would struggle without them.
  4. Off-the-shelf software that was bought, tried and never quite fit.
  5. A quote for custom-built software that came back at six figures and a year.
  6. An owner who would rather pay for what is delivered than for hours.

If the Answer Is No Build

A Blueprint may conclude that no build is needed.

Questions

What happens if we decide not to build?

The Blueprint is complete at the playback. The fee covers it, and nothing further is owed. If you go on to Release 1, the fee is credited against it.

Does the Blueprint commit us to a build?

No. Each release is a separate decision, priced before it starts.

Can a Blueprint cover more than one process?

Yes. The proposal names the processes in scope; more processes or more people lengthen the Blueprint towards four weeks, and the fee is set accordingly before work starts.

Do we need to prepare anything?

No written brief. A list of the people who carry out the process, and read access to the records it runs on, are enough to begin.

How long before software is running?

Release 1 starts after the playback, once its price and scope are agreed. Its length, two to four weeks, is set in the plan.

Start a Conversation

Start a Conversation

Tell us which process you would change first. A senior Wikker lead replies within one business day with a view on whether a Blueprint makes sense.