How we think about innovation

Our approach is shaped by one belief: the best innovation process is the one a team can actually run themselves, repeatedly, without outside help.

Team members reviewing a project plan spread across a large table

What guides everything we do

These are not abstract values. They are specific choices that show up in how every session is designed and how we interact with your team.

A

Learning before deciding

Before committing to an idea, teams should understand what they do not yet know about it. Our sessions start by surfacing assumptions and identifying the cheapest way to test them. This prevents expensive mistakes and makes decisions feel grounded rather than arbitrary.

B

Concrete over conceptual

Ideas stay abstract for too long. The moment you make something physical, even a rough sketch or a cardboard model, the conversation changes. People can react to something real. Vague disagreements become specific and solvable. We push toward tangible output in every session.

C

Speed reduces cost

The longer you spend refining an idea before testing it, the more invested you become in being right. Moving fast and testing early keeps your attachment low and your learning high. We design sessions to generate testable output quickly, not polished output slowly.

D

Teams own the process

Everything we teach is designed to be run by your team without us. Facilitating your first session with us is the starting point. Running your fifth session on your own is the goal. We measure success by how little you need us after the program ends.

A repeatable cycle

The Wigulu method is not linear. It is a loop. Each pass through the cycle builds confidence and reduces uncertainty about the idea you are developing.

Focus
Build
Test
Learn

Focus

Identify the single most important assumption to test. Not five assumptions. One. This discipline is where most of the value in the method comes from.

Build

Create the smallest version of something that lets you test that assumption. This might take two hours. It should not take two weeks.

Test

Put it in front of real people. Watch what they do, not just what they say. Ask open questions. Listen more than you talk.

Learn

Decide what you now know that you did not know before. Update your idea. Identify the next assumption. Start the cycle again.

Team member creating a paper prototype during a rapid prototyping session

What you actually do in sessions

We use a curated set of tools that are easy to learn and genuinely useful. None of them require special training or expensive software. Each one is selected because it produces something your team can act on, not just something that looks good in a presentation.

Impact-Effort Matrix A simple grid for comparing ideas on two dimensions at once, without endless debate.
Assumption Mapping Identifying what you believe to be true about your idea and sorting by risk.
Story Sketching Drawing a simple sequence of how a user would experience your idea. Fast and clarifying.
Discovery Interviews Structured conversations with five to eight people that replace months of market research.

What this approach is not

Not a strategy consulting engagement

We do not produce market analyses, opportunity assessments, or strategic roadmaps. Other firms do that well. We focus on what comes after: turning chosen ideas into something testable.

Not a product development service

We do not build your product. We help your team build a prototype version quickly, so you can learn before investing in the real thing. The building is always done by your people.

Not an ongoing retainer service

We are not designed to be a permanent presence in your organization. The program has a clear beginning and end. Independence is the outcome, not continued reliance on external support.

Want to see the methodology in action?

We are happy to walk through a specific example with your team. Get in touch and we can find a time that works.

Get in Touch