Skip to main content
Learn.

Catalog / Studio practice

Project process
checklist.

A public version of the studio workflow Jambo trainees should learn: discovery, scope, brief, design review, handoff, launch, and follow-up.

Handoff packet

Responsive notesComponent statesCopy statesAnalytics events
1

Qualify the request

Decide whether the project is real, valuable, and a good fit before the team spends design time.

  • Confirm the business goal, audience, timeline, and expected budget range.
  • Ask what success will look like after launch.
  • Name the decision maker and the person responsible for feedback.
  • Avoid long calls before the scope and budget are roughly aligned.
2

Run discovery

Turn vague client context into usable design inputs.

  • Collect the business story, offer, audience, competitors, and brand direction.
  • Ask for existing analytics, conversion data, customer objections, and support questions when available.
  • Gather visual references with reasons, not just links.
  • Write down constraints: platform, content, languages, integrations, launch date, and maintenance owner.
3

Define scope

Make the work measurable before design starts.

  • Write the pages, sections, deliverables, review rounds, and excluded work.
  • Split larger work into milestones with clear acceptance points.
  • Keep price changes tied to scope changes, not pressure.
  • Document payment timing, content deadlines, and what happens when feedback is late.
4

Create the brief

Give everyone one shared reference for what is being built and why.

  • Summarize the project goal in plain language.
  • List the project team, communication channel, meeting rhythm, and available hours.
  • Link the discovery notes, statement of work, assets folder, and timeline.
  • Call out assumptions and open questions before moving to wireframes.
5

Design and review

Move from structure to polished UI without losing the original problem.

  • Start with sitemap, rough sections, and low-fidelity wireframes.
  • Create mood boards or references before locking visual direction.
  • Turn the chosen direction into a style guide for type, color, spacing, and components.
  • Review designs with a script: goal, what changed, what needs feedback, and the deadline.
6

Handoff and launch

Make the final design buildable, testable, and safe to release.

  • Include responsive frames, component states, assets, copy, interaction notes, and edge cases.
  • Check accessibility, forms, empty states, error states, loading states, analytics, and metadata.
  • Run a pre-launch review on real devices and a test URL.
  • Confirm post-launch ownership for backups, updates, security, content, and support.