Idea / Working hypothesis
Working title / Concept onlyA career has chapters. Not just rows.
Show where you have been, what challenged you and what you can do now. Distinctive in expression. Clear enough to understand at a glance.
01 / Possible path
From a job history to a person understood.
- Map the chapters
Bring roles, education, personal projects and important turning points into a clear timeline.
- Show the challenge
Give each chapter context: what needed to change, what was difficult and what you took responsibility for.
- Connect the capability
Link skills to actual work, decisions, outcomes and lessons—not a disconnected list of keywords.
- Share the story
Let someone scan the essentials first, then explore the chapters and examples that matter to them.
02 / Story structure
Context makes capability visible.
Your experience
- Previous roles
- Education
- Side projects
- Challenges and turning points
What people understand
- What you have done
- How you approach problems
- What you can contribute
- Where you want to go
Visual storytelling should make a career easier to understand, not make a recruiter work harder to find the essentials.
03 / Opportunity horizons
One story. Different depths.
- The first impression
A concise overview of the person, their experience and the contribution they want to make next.
- The chapters
A visual journey through roles and projects, with room for transitions, unconventional paths and lessons learned.
- The evidence
Selected work and concrete examples behind each capability. A future connection to Skill Atlas could keep that picture growing.
04 / Open decisions
What the first prototype should prove.
- First audienceTo define
- Which career paths benefit most—and what do their hiring teams need to understand first?
- Clarity testTo define
- Can someone quickly find previous roles, relevant skills and the strongest examples?
- Sharing formatTo define
- How should a personal link and a readable export fit existing application workflows?
- Personal controlTo define
- Which chapters are public, selectively shared or kept private?