When to start working
Overview
This framework helps designers understand when they have enough information to begin the design process, balancing the need for clarity with the ability to work efficiently and proactively.
🎯 Guiding Principle
"Designers can start working as soon as they have some clarity about the project. You don't need to wait for perfect information—but you do need enough context to design with purpose."
📅 Understanding the Timeline
Client-Facing Design Phase
Begins according to the official project timeline
This is when design work is formally presented and shared with the client
Internal Design Phase
Can start as soon as you have basic clarity about the project
You don't need to wait for the Refinement Phase to be fully completed
Allows you to work proactively and be ready when the official phase begins
✅ When You CAN Start Working
You have enough clarity to begin when you can answer these questions:
Minimum Clarity Requirements
What problem are we solving? - You understand the core user need or business goal
Who are we designing for? - You know the primary user type(s) and their context
What are the main features/flows? - You have a general sense of what needs to be designed
What are the success criteria? - You understand what "done" looks like
You Can Start With:
Foundational Work
A draft low-fidelity wireframe: Even if we don’t have full clarity yet, starting to think through the screens will naturally lead us to ask key questions that are fundamental to the flow and overall experience.
A draft pipeline - If applicable (fundamental when apps require this type of resource)
Profile and account settings screens
Login & onboarding structure
Basic file setup in Figma (cover, brand colors if available)
File & System Setup
Set up your Figma files with proper structure
Create the file cover with project information
Define brand colors (if provided by the client)
Create a project, copy paste the baste file and add the Figma file link to the specific channel slack
Preparation
Gather inspiration and references
Key point: This early work is exploratory and flexible. You're building understanding, not committing to final solutions.
This framework is living documentation. If you encounter situations not covered here or have suggestions for improvement, share feedback with the team.