ICB IT COULD BE

Manchester imagination studio

What if the next useful thing is already waiting inside your team?

IT COULD BE (ICB) LTD helps organisations explore ideas, shape digital services, simplify internal systems, and turn uncertain opportunities into clear experiments. We work where curiosity meets practical delivery: research, prototypes, workflows, content systems, service journeys, and measurable pilots.

Question What could improve the customer journey?
Prototype Can we test the idea in two weeks?
Evidence What did users actually do?
Service design Digital discovery Workflow mapping Prototype sprints Knowledge systems Team enablement

Studio belief

Ideas become valuable when they are described clearly, tested honestly, and connected to daily work.

Many organisations have more ideas than capacity. They can see improvements, new services, better internal tools, clearer content, or new customer experiences, but the path from possibility to delivery feels vague. We provide a structured, lightweight way to investigate what could be useful before large investments are made.

Our work is deliberately practical. We translate broad ideas into user stories, service maps, clickable prototypes, operational requirements, decision notes, pilot plans, and team rituals. The output is not a glossy presentation that sits unread. It is a living set of materials that helps people make decisions and move.

01

Opportunity Discovery

For teams with a broad challenge, a stalled idea, or a market question. We interview stakeholders, review existing materials, map assumptions, and identify the smallest meaningful experiment.

  • Stakeholder interviews and synthesis
  • Assumption mapping and risk scoring
  • Service journey analysis
  • Decision-ready discovery report

02

Prototype Sprint

A focused build-and-learn cycle for testing a concept without committing to a full product build. Useful for portals, onboarding journeys, dashboards, booking flows, and content-heavy services.

  • Wireframes and clickable flows
  • Content structure and messaging
  • User feedback sessions
  • Next-step delivery backlog

03

Workflow Redesign

For internal processes that depend on spreadsheets, repeated emails, unclear approvals, duplicate entry, or informal knowledge held by a few busy people.

  • Current-state process mapping
  • Role and responsibility clarification
  • Automation opportunities
  • Practical implementation roadmap

04

Knowledge System Design

For organisations that need clearer documentation, repeatable playbooks, searchable knowledge bases, onboarding guides, or better internal content governance.

  • Information architecture
  • Editorial standards
  • Template libraries
  • Maintenance routines

The ICB method

From "it could be" to "we know what to do next".

Listen

We gather context from people closest to the work: staff, customers, managers, service teams, partners, and operational owners.

Frame

We define the real problem, the desired outcome, the constraints, the current workarounds, and the assumptions that need testing.

Make

We create tangible artefacts such as maps, prototypes, copy, diagrams, decision notes, scripts, or process models.

Learn

We test with users or stakeholders, collect evidence, document what changed, and recommend the next sensible move.

Studio canvas

Every engagement leaves behind a clearer operating picture.

We like artefacts that teams can reuse. Depending on the challenge, a project may produce a service blueprint, prioritised backlog, prototype, content model, workflow map, system requirements, interview insights, governance checklist, or launch plan. These materials reduce ambiguity and help future suppliers, internal teams, or leadership groups keep momentum.

Customer promise
Operational reality
Data and systems
People and roles
Risks and assumptions
Prototype evidence
Content and language
Next decisions

Field notes

Patterns we help teams untangle.

The spreadsheet that became a system

A team may not need a complex platform at first. Sometimes the right move is to understand why the spreadsheet exists, what decisions it supports, which fields matter, and where errors enter the process.

The idea that needed a smaller test

Large digital ideas often become easier when reduced to one audience, one journey, one promise, and one measurable experiment that can be observed quickly.

The service that needed better words

Confusing language can make a good service feel difficult. We help teams rewrite journeys, instructions, forms, and support content around how people actually think.

Useful outcomes, not theatre.

Clearer decisionsLeadership can see the options, evidence, cost range, and trade-offs.
Better team alignmentPeople share the same map of the problem and the intended direction.
Lower delivery riskAssumptions are tested before heavy build commitments are made.
Reusable assetsProject outputs become guidance for future delivery, procurement, or internal work.