First day, first week, first prototype

First dayCopy Anchor Link

Get access to the necessary repositories. Start the playbook, read the operating model and identify sources of truth. Open a real UX record and find the link from a story to its validation scenario.

Outcome: you know where to find the method, research, visual contract and components.

First weekCopy Anchor Link

Start the product and Storybook following local READMEs. Examine a primitive, a pattern and a page. Open a UX Planner demo and a VariantHub comparison. After setup, open a new session in your AI coding tool and use jado-run for a scoped assignment. Read the JADO route from entry to handoff. Open a role procedure and identify the conditions that activate its skills.

Outcome: you can choose the tool for the question and distinguish exploration from production.

First prototypeCopy Anchor Link

Choose a focused design question with a stakeholder. Gather evidence and competitor references, clarify the message, connect stories and flows and prepare a prototype with documented components. Agree on a user test, synthesize observations and share the proposal and limitations. Any contribution through a PR follows team agreements.

First design reviewCopy Anchor Link

Read the contract, observe the path, record reproducible findings and separate UX risks from aesthetic preferences. Propose a change with an observable success criterion.

Adapt it to the teamCopy Anchor Link

Each team sets its own onboarding contact, repository and tool access, schedule, first products and autonomy criteria. This route is a proposal based on the tools described here.