Test before you scale

An innovation and experimentation lab.

We help organisations, governments and entrepreneurs understand problems, test ideas and build practical solutions.

When the answer isn't obvious, we research the problem, explore the options and test what works.

Work with us →Explore our work →
A team maps ideas with sticky notes on a glass wall.

Engagements for

The u.lab framework

How we work →
  1. 01

    Problem

    Define what is really happening

  2. 02

    Research

    Study options before choosing one

  3. 03

    Experiment

    Test the smallest useful version

  4. 04

    Evidence

    Measure what actually changed

  5. 05

    Decision

    Build, change course or stop

Why we exist

Some problems need more than advice.

A government department wants to improve a public service. A company wants to know whether AI can actually improve its operations. A founder has an idea but doesn't know whether customers will use it. An institution wants to digitise a process but doesn't know where to start.

These problems don't always need another report or presentation. Sometimes they need someone to investigate the problem, build something and test it.

That's where u.lab comes in.

Start a conversation →

What we do

Four capabilities. One practical approach.

Complex problems rarely fit neatly into one discipline. We combine research, strategy, experimentation and building according to what the problem requires.

  1. 01

    Research

    We investigate the problem, the people affected, the market, the technology and the wider context. The aim is to understand what is actually happening before deciding what to do.

    • Market research
    • User research
    • Technology research
    • Competitive analysis
    • Emerging technology intelligence
    Research in detail →
  2. 02

    Strategy

    We turn findings into choices. We assess opportunities, evaluate alternatives and help organisations determine where to focus their attention and resources.

    • Opportunity assessments
    • Product strategy
    • Technology strategy
    • Business models
    • Innovation strategy
    Strategy in detail →
  3. 03

    Experimentation

    We test important assumptions before larger commitments are made. This can involve prototypes, pilots, user testing, process experiments or technology trials.

    • Prototypes
    • Pilots
    • Proofs of concept
    • User testing
    • Process experiments
    • Technology trials
    Experimentation in detail →
  4. 04

    Building

    When an idea is worth pursuing, we help turn it into something practical. This may include a digital product, AI application, internal tool, prototype, programme or new venture.

    • MVPs
    • Digital products
    • AI solutions
    • Internal tools
    • Prototypes
    • Venture concepts
    Building in detail →

Not every problem requires all four capabilities. We use the combination that makes sense for the challenge.

See the full method →

Working with institutions

Clear expectations before the work begins.

Organisations need to understand how an external team will approach their people, information and operations. We believe those expectations should be agreed before an engagement begins.

  1. 01

    Confidentiality and discretion

    We approach sensitive organisational information with care. Confidentiality expectations and permitted use of information should be agreed before work begins.

  2. 02

    Defined scope and ownership

    Every engagement should have a clear brief covering the problem, objectives, activities, deliverables, responsibilities and ownership of outputs.

  3. 03

    Proportionate data access

    We seek to work with only the information necessary for the agreed task. Access requirements and responsibilities should be established in advance.

  4. 04

    Working within your requirements

    Organisational policies, procurement processes, security expectations and applicable data requirements should inform the design of the engagement.

  5. 05

    Evidence that can be examined

    We aim to document our approach, assumptions, findings and recommendations so that decision-makers can understand and assess the work.

  6. 06

    Building institutional capability

    Our objective is to leave organisations better equipped to make decisions and take the next step. Where appropriate, we incorporate knowledge transfer and handover into the engagement.

Specific contractual, confidentiality, data-handling and compliance arrangements are agreed according to the nature and requirements of each engagement.

Request a briefing →

Programmes & Labs

Programmes designed around real problems.

u.lab designs and facilitates programmes that bring people, expertise and practical experimentation together around a defined challenge. Some engagements help an organisation explore an opportunity. Others develop new capabilities, test solutions or bring an ecosystem together.

A team talks around a meeting table with laptops open.

Programme catalogue

Six areas

  1. 01

    Entrepreneurship & Venture Building

    Helping founders move from an idea to evidence a venture is worth building.

    What it addresses
    Founders and institutions with venture ideas that have not yet been tested against real customers or markets.
    What we can design
    Venture-building programmes, customer-discovery sprints and validation labs built around business-model design and early prototyping.
    What it can help produce
    Validated — or deliberately rejected — venture concepts, customer evidence, early prototypes and go-to-market plans.

    Formats may include

    • Customer discovery
    • Problem validation
    • Business model design
    • Market research
    • Go-to-market strategy
    • Prototyping
    • Venture experimentation
    u.lab for entrepreneurs →
  2. 02

    AI & Emerging Technology

    Finding where AI and new technology can genuinely help, and testing it safely.

    What it addresses
    Organisations under pressure to adopt AI or emerging technology without a clear view of where it would pay off.
    What we can design
    Opportunity-discovery workshops, AI experimentation labs and adoption programmes that test technology safely on real tasks.
    What it can help produce
    AI opportunity assessments, tested use cases, responsible-use guidelines and implementation roadmaps.

    Formats may include

    • AI strategy
    • Opportunity discovery
    • AI experimentation
    • Emerging tech intelligence
    • Adoption workshops
    • Future-of-work exploration
    • Responsible tech experimentation
    u.lab for business →
  3. 03

    Innovation Labs & Challenges

    Structured formats that bring people together to solve a defined problem.

    What it addresses
    A defined problem that would benefit from fresh ideas, outside expertise or a structured way to test options quickly.
    What we can design
    Innovation challenges, design sprints, problem-solving labs and pilot programmes with a clear brief and evaluation criteria.
    What it can help produce
    Shortlisted and prototyped concepts, pilot designs and evidence on which ideas merit further investment.

    Formats may include

    • Innovation challenges
    • Design sprints
    • Problem-solving labs
    • Rapid experimentation
    • Prototyping
    • Pilot programmes
    • Innovation competitions
    See how experiments are designed →
  4. 04

    Public Sector Innovation

    Practical experimentation for better public services and policy.

    What it addresses
    Public services, processes and policies that need to improve, where large-scale reform would be costly to get wrong.
    What we can design
    Service-redesign labs, policy experiments, digital transformation pilots and capacity-building programmes for public teams.
    What it can help produce
    Service journey maps, tested service prototypes, policy experiment designs and recommendations on what to scale.

    Formats may include

    • Public service innovation
    • Digital transformation
    • Policy experimentation
    • Government AI exploration
    • Service redesign
    • Future scenarios
    • Capacity building
    u.lab for government →
  5. 05

    Ecosystem & Train-the-Trainer

    Building the people and institutions that can run this work themselves.

    What it addresses
    Institutions that want to run problem-solving and venture programmes themselves, and strengthen the ecosystem around them.
    What we can design
    Facilitator training, curriculum development, reusable programme frameworks and ecosystem-mapping exercises.
    What it can help produce
    Trained facilitators, programme frameworks, curricula and ecosystem maps that stay with the institution.

    Formats may include

    • Facilitator training
    • Programme design
    • Curriculum development
    • Train-the-trainer
    • Ecosystem mapping
    • Community building
    • Institutional capacity building
  6. 06

    Defence & Dual-Use

    Bringing the technology ecosystem together around the strategic problems shaping defence, security, resilience and critical infrastructure.

    What it addresses
    Strategic problems in defence, security, resilience and critical infrastructure that call for technology from beyond traditional suppliers.
    What we can design
    Innovation challenges, technology demonstrations, defence innovation sprints and field experiments connecting startups, researchers and government.
    What it can help produce
    Technology scouting findings, demonstration results, pilot designs and cross-sector working groups.

    Formats may include

    • Innovation challenges
    • Technology demonstrations
    • Startup–government collaboration
    • Defence innovation sprints
    • Pilots & field experiments
    • Technology scouting
    • Cross-sector working groups
    Explore the Defence Lab →

Have a programme in mind?

We can help shape the brief, design the approach and determine what a useful programme should achieve.

Discuss a programme →

Engagement pathways

Problems we work on.

Different organisations face different challenges. Here are some of the problem areas where research, strategy and practical experimentation can help move things forward.

Pathway 01 · Rethinking a public service

The organisational challenge

A public service is slow or difficult to use, and the cause of the delay is unclear even to the people who run it.

The question
Where in the service does the delay actually originate — and which single change would make the most difference?
How it could run
An engagement could begin with mapping the service journey and observing it at one site. A possible approach would involve piloting one redesigned step before any wider rollout.
Potential outputs
Potential outputs include a service journey map, a tested redesign of one step and a recommendation on whether to scale it.
Discuss a similar problem →

These are examples of the types of engagements u.lab can design and undertake. The scope, approach and outputs of each engagement are developed around the organisation's specific needs.

Outputs

What an engagement can produce.

The value of an experiment is not simply the idea it produces. It is the evidence, insight or practical output that helps an organisation decide what to do next.

A person works on code and a web page on a laptop.
  1. 01Potential output

    AI opportunity assessment

    Question investigated

    Where does the organisation lose the most time through repetitive work — and where could AI genuinely help?

    Type of work
    Process mapping, workflow analysis and targeted AI trials on a small number of tasks.
    Possible deliverable
    An assessment ranking opportunities by likely value, cost and risk.
    Decision it informs
    Which AI applications to invest in, pilot further or set aside.
  2. 02Potential output

    Venture validation

    Question investigated

    Will the people this is built for actually use it — and pay for it?

    Type of work
    Customer interviews, a study of current alternatives, a low-cost prototype and a small test with real users.
    Possible deliverable
    A validation report setting out the evidence for and against demand.
    Decision it informs
    Whether to build, change or stop.
  3. 03Potential output

    Public-service prototype

    Question investigated

    Can one redesigned step reduce delay under real operating conditions?

    Type of work
    Service journey mapping, observation at a single site and a small-scale pilot.
    Possible deliverable
    A working prototype of the redesigned step, with measurements from the pilot.
    Decision it informs
    Whether to scale the change, adjust it or test another option.
  4. 04Potential output

    Emerging-technology assessment

    Question investigated

    Does this technology perform under local conditions — infrastructure, cost, skills and regulation?

    Type of work
    Technology review, an assessment of local constraints and a controlled field trial.
    Possible deliverable
    An assessment of viability and the adaptation the technology would need.
    Decision it informs
    Whether the technology is worth pursuing here, and on what terms.
  5. 05Potential output

    New product or service concept

    Question investigated

    Which version of this product or service, for which market, is worth developing first?

    Type of work
    Market research, business-model options and small launch experiments with early customers.
    Possible deliverable
    A defined concept with early customer evidence and a working business model.
    Decision it informs
    Where to direct a larger investment.

A u.lab principle

Evidence is more useful than enthusiasm.

Start a conversation →Open the experiment library →

How we work

A method with five stages.

Every engagement follows the same discipline, whatever its size: a clear question, honest research, a bounded test, documented evidence and a decision.

  1. 01

    Problem

    We start with the problem: what is happening, who is affected, what is known — and what isn't.

  2. 02

    Research

    We research possible approaches, technologies, markets and solutions before choosing one.

  3. 03

    Experiment

    We build the smallest useful experiment and put it into real conditions.

  4. 04

    Evidence

    We look at what happened: what worked, what didn't and what surprised us.

  5. 05

    Decision

    We use what we learned to build, change course, run another experiment — or stop.

The principle
"We don't need every experiment to succeed. We need every experiment to produce useful information."

Why u.lab

What we do differently.

  1. 01

    The problem before the technology.

    We don't force every problem into a predetermined solution. The question comes first; the tool follows.

  2. 02

    Assumptions tested before resources are committed.

    Small experiments can prevent expensive mistakes. A good idea is only a hypothesis until it meets reality.

  3. 03

    Practical solutions, not recommendations alone.

    Sometimes research is enough. When a prototype is needed, we build it.

  4. 04

    Knowledge and capability transferred.

    We hand over what we learned, and how we learned it, so your team can carry the work forward.

Technology, research, business, design and strategy, brought together around one question.

Difficult questions

The questions we find interesting.

  • We would map where time is actually lost, then test AI on one narrow task before anyone signs a platform contract.

We don't always know the answer. That's the point. We experiment.

Start here

You don't need to have the solution. Start with the problem. Tell us what you're trying to figure out, and we'll help determine what needs to be researched, tested or built.

Start a conversation →problems@ulabworks.co.zw