Discuss an initiative

01 / Approach

Move only as far as the evidence responsibly allows.

Luminor does not force every initiative through the same sequence of activities.

The work starts with the choice in front of the team, surfaces what is genuinely unknown about it, and does whatever is required to settle it with confidence.

See how the work moves

02 / The working standard

The method is flexible. The standard is not.

The activities change with the initiative. These four conditions remain present throughout the work.

01

Decision before deliverable.

Every activity must improve a real choice, not simply produce another document.

On a project: each phase is named for the question it retires, and workshops end with owners and next steps, not just notes.
02

Evidence before certainty.

Assumptions are made visible, tested in proportion to their risk, and revised when the evidence changes.

On a project: an assumption log travels with the work, listing what would have to be true and what we have seen so far.
03

Operations inside the product.

Workflows, policy, data, roles, and service handoffs are designed with the customer experience—not after it.

On a project: staff screens and policy constraints appear in the design files beside the customer journey.
04

Access from the beginning.

Accessibility, comprehension, and inclusive use shape the structure and interaction from the first model onward.

On a project: the first prototype is tested for accessibility; it is never left for a final audit.

03 / Three movements

A flexible route from uncertainty to useful implementation.

Not every engagement begins at movement one or requires all three. The starting point is wherever the unresolved decision carries the most risk.

Movement 01Orient

See the real system before choosing a direction.

Understand the service as it operates today, then define the opportunity worth pursuing.

Movement 02Prove

Make the direction tangible and challenge it early.

Turn product intent into a model that can be tested against people, policy, accessibility, operations, and technology.

Movement 03Realize

Carry product intent into real use.

Support dependable implementation, then use live behaviour and operational evidence to decide what should improve next.

04 / Evidence ledger

Each stage earns the next.

Six stages, each closing with something you can hold: a finding, a direction, a tested model, a working release. The ledger doubles as a shared record of what was asked, learned, and decided, so no one has to reconstruct why the product looks the way it does.

01Discover

Establish the real starting point.

Question

What is happening now, for whom, and under which organizational, operational, policy, and technical conditions?

Evidence

  • Stakeholder and user conversations
  • Current product and service review
  • Workflow and constraint mapping
  • Existing data and research
Decision stateThe current environment is visible.
02Define

Turn evidence into a shared direction.

Question

Which problem deserves investment, what outcome matters, and which assumptions still need to be resolved?

Evidence

  • Problem and opportunity framing
  • Product vision and principles
  • Scope and priority decisions
  • Measures of success
Decision stateThe opportunity and boundaries are aligned.
03Design

Make the product logic tangible.

Question

How should the service, workflow, information, and interface work together for every important role and state?

Evidence

  • Journey and task models
  • Information architecture
  • Workflow and interaction design
  • Accessible interface prototypes
Decision stateThe direction can be seen and used.
04Validate

Test the decisions carrying the greatest risk.

Question

Where do user expectations, policy, accessibility, operations, product logic, and technical reality fail to align?

Evidence

  • Concept and usability testing
  • Accessibility evaluation
  • Stakeholder and operational walkthroughs
  • Technical feasibility review
Decision stateCritical assumptions have been challenged.
05Deliver

Protect intent through implementation.

Question

What must design, engineering, content, operations, and leadership understand to deliver the intended experience accurately?

Evidence

  • Component and state specifications
  • Responsive and interaction guidance
  • Design and engineering reviews
  • Quality and launch criteria
Decision stateThe product is ready to implement and release.
06Improve

Let real use guide what happens next.

Question

What is the product now revealing about behaviour, service performance, operational friction, and the next valuable change?

Evidence

  • Product and service performance
  • User and operational feedback
  • Follow-up research
  • Roadmap and system evolution
Decision stateLive evidence informs the next priority.

05 / Engagement shape

The work expands or contracts around the decision.

These are useful starting structures—not fixed packages.

Focused

Decision sprint

Resolve one important question through targeted research, framing, design, or validation.

2–6 weeks
Connected

Product initiative

Move from uncertain direction through a validated product model and supported implementation.

Multi-phase
Embedded

Product partnership

Strengthen an established team with ongoing strategy, research, design, systems, or delivery capability.

Ongoing

06 / Start with the uncertainty

Come with the question, not the brief.

Describe what the organization is trying to improve and where confidence runs out. We will suggest the shortest responsible path to a next step.

Start a conversation