craftnotion
Book a Call

Process

We start with what exists, make important decisions explicit, and agree how the work moves toward release, continuation, or handoff.

Different starting points

Build, Improve, and Continue
need different first decisions.

A new product needs framing. Existing software needs context. Ongoing work needs a clear roadmap and responsibility boundary.

Phase 01 of 05
Deliverable:
A shared starting brief with decisions still visible.

Discovery

Understand what exists before deciding what to build.

We map the requirement, users, workflows, constraints, and available evidence. For an existing product, that includes the current codebase and changes already in flight.

Core Activities in this Phase
01.

Requirement Context

Clarify the business situation, users, desired change, and technical boundaries.

02.

Workflow Mapping

Map user journeys and system touchpoints to expose friction and gaps.

03.

Open Questions

Surface assumptions, dependencies, and constraints before sequencing the work.

Phase 01 of 05
Deliverable:
A shared starting brief with decisions still visible.

Discovery

Understand what exists before deciding what to build.

We map the requirement, users, workflows, constraints, and available evidence. For an existing product, that includes the current codebase and changes already in flight.

Core Activities in this Phase
01.

Requirement Context

Clarify the business situation, users, desired change, and technical boundaries.

02.

Workflow Mapping

Map user journeys and system touchpoints to expose friction and gaps.

03.

Open Questions

Surface assumptions, dependencies, and constraints before sequencing the work.

Phase 02 of 05
Deliverable:
A plan the team can review and execute.

UX / Planning

Turn the requirement into an ordered product and technical plan.

We shape the user journey, interface states, scope, sequence, architecture, and integrations so the plan reflects the product priorities.

Core Activities in this Phase
01.

User Journeys

Define the key journeys, interface states, and decisions the product must support.

02.

Scope and Sequence

Break the work into milestones and increments that can be reviewed in context.

03.

Architecture Decisions

Align technical direction and integrations with the product requirements.

Phase 03 of 05
Deliverable:
Working software for the next review.

Development

Build in reviewable increments around the agreed priorities.

We build in increments so decisions can happen while the product is taking shape, with the review rhythm agreed for the engagement.

Core Activities in this Phase
01.

Incremental Delivery

Develop the next useful slice of the product around the agreed priorities.

02.

Frontend and Backend

Coordinate interface surfaces, APIs, and data around real product workflows.

03.

Review Points

Create review moments that let decisions happen with the right context.

Phase 04 of 05
Deliverable:
A release candidate with open issues and sign-off criteria visible.

QA & Pre-launch

Define release readiness for the actual scope.

We test how the system works together under normal and edge conditions, applying cross-browser, device, regression, and performance checks where the product requires them.

Core Activities in this Phase
01.

Core Flow Verification

Test functional user journeys, error handling, and state logic within scope.

02.

Cross-device Checks

Verify responsive rendering and supported browsers or mobile viewports where relevant.

03.

Targeted Regression

Check performance and connected workflows for regressions that affect release readiness.

Phase 05 of 05
Deliverable:
A release path and next-step agreement.

Release & next steps

Release, continue, or hand over with the next boundary agreed.

We prepare the release, support the agreed handoff or continued development, and document what the next team needs to operate or extend the product.

Core Activities in this Phase
01.

Release Preparation

Coordinate the deployment steps, environments, and release checks required by the scope.

02.

Handoff or Continuation

Agree whether the next stage is a handoff, roadmap work, or ongoing product engineering.

03.

Access and Documentation

Set expectations for repository access, working context, and next-step documentation.

Delivery boundaries

Make the working agreement explicit.
before build and release.

The engagement sets review cadence, ownership terms, documentation, and release responsibilities.

Review01

Review cadence

We agree how progress and decisions will be reviewed and what evidence is available at each decision point.

Handoff02

Handoff terms

Repository, assets, documentation, and intellectual property follow the applicable agreement and payment terms.

Release03

Release and operating notes

We define the environments, access, testing, deployment, and next-step information that the scope requires.

FAQ

Process decisions and delivery boundaries,
answered clearly.

Common questions about starting points, review cadence, scope changes, and next-step responsibilities.

Build starts with a requirement that needs definition. Improve starts with an existing product, codebase, or workflow. Continue starts with an active roadmap and an agreed responsibility boundary.

Start with context.
Discuss the work.

Discuss the work