Askniels project
Building the operating system of a methodology
timeframe
2 years
tools
Figma Cursor Gemini
category
AI - UX - UI - REACT
View it Live
The problem
We were helping organizations build better human experiences. But the methodology itself was hard to appropriate. Not because it was complex — because it had no home.
Coaches and teams had the knowledge. They didn't have the structure to make it theirs. Every project started with the same blank page. Every new team member rebuilt the same mental models from scratch.
The real challenge wasn't documentation. It was autonomy — giving people a framework solid enough to rely on, flexible enough to fit their actual work, and integrated enough to survive contact with a real project schedule.
Today
The platform is live in production. Teams onboard the methodology without a coach in the room. Activities are structured but not rigid — they adapt to the project, not the other way around. The framework holds across different profiles, different schedules, different levels of methodology maturity.
What changed: people stopped asking "what do we do next?" and started making that call themselves. Less friction, more flow. The kind of shift that's hard to design for — and obvious when it happens.
There's still ground to cover. But the foundation is there, and so is the intent: make the methodology feel like a natural part of how people work, not an extra layer on top of it.
From blank canvas to delivery, faster
The core design challenge wasn't building features. It was making a complex methodology feel effortless to use mid-project.
A team in the middle of an ideation sprint doesn't want to stop and read documentation. They need the right activity at the right moment, assembled into a workplan that reflects where they actually are — not a generic template that forces them into a process that doesn't fit.
The Plan Builder was designed around this tension. A visual, drag-and-drop canvas where teams compose their own project arc from structured methodological activities — seeing the full shape of a project at a glance, adapting it as the work evolves. Not a rigid framework. A living structure.
The AI assistant sits inside that workspace, context-aware, trained on the method. When a team hits a decision point, it doesn't redirect them to a knowledge base. It meets them where they are.
−54%
time to project delivery
57
structured activities, ready to use
06
project phases, fully integrated
97
Lighthouse score
WHAT THE FIELD CHANGED
- The first Plan Builder gave teams complete freedom from day one. Too much open space created paralysis, not creativity. Starter templates weren't in scope — real usage made them essential.
- Progressive activity discovery replaced the full catalogue view. Exposing 57 activities at once overwhelmed teams mid-project. Surfacing them by phase, at the right moment, changed how teams engaged with the method entirely.
- The AI assistant revealed how much strategic knowledge had never been formalised. Building it forced the kind of documentation that makes a methodology truly transferable.
Askniels project
Building the operating system of a methodology
timeframe
2 years
tools
Figma Cursor Gemini
category
AI - UX - UI - REACT
View it Live
The problem
We were helping organizations build better human experiences. But the methodology itself was hard to appropriate. Not because it was complex — because it had no home.
Coaches and teams had the knowledge. They didn't have the structure to make it theirs. Every project started with the same blank page. Every new team member rebuilt the same mental models from scratch.
The real challenge wasn't documentation. It was autonomy — giving people a framework solid enough to rely on, flexible enough to fit their actual work, and integrated enough to survive contact with a real project schedule.
Today
The platform is live in production. Teams onboard the methodology without a coach in the room. Activities are structured but not rigid — they adapt to the project, not the other way around. The framework holds across different profiles, different schedules, different levels of methodology maturity.
What changed: people stopped asking "what do we do next?" and started making that call themselves. Less friction, more flow. The kind of shift that's hard to design for — and obvious when it happens.
There's still ground to cover. But the foundation is there, and so is the intent: make the methodology feel like a natural part of how people work, not an extra layer on top of it.
From blank canvas to delivery, faster
The core design challenge wasn't building features. It was making a complex methodology feel effortless to use mid-project.
A team in the middle of an ideation sprint doesn't want to stop and read documentation. They need the right activity at the right moment, assembled into a workplan that reflects where they actually are — not a generic template that forces them into a process that doesn't fit.
The Plan Builder was designed around this tension. A visual, drag-and-drop canvas where teams compose their own project arc from structured methodological activities — seeing the full shape of a project at a glance, adapting it as the work evolves. Not a rigid framework. A living structure.
The AI assistant sits inside that workspace, context-aware, trained on the method. When a team hits a decision point, it doesn't redirect them to a knowledge base. It meets them where they are.
−54%
time to project delivery
57
structured activities, ready to use
06
project phases, fully integrated
97
Lighthouse score
WHAT THE FIELD CHANGED
- The first Plan Builder gave teams complete freedom from day one. Too much open space created paralysis, not creativity. Starter templates weren't in scope — real usage made them essential.
- Progressive activity discovery replaced the full catalogue view. Exposing 57 activities at once overwhelmed teams mid-project. Surfacing them by phase, at the right moment, changed how teams engaged with the method entirely.
- The AI assistant revealed how much strategic knowledge had never been formalised. Building it forced the kind of documentation that makes a methodology truly transferable.
Askniels project
Building the operating system of a methodology
timeframe
2 years
tools
Figma Cursor Gemini
category
AI - UX - UI - REACT
View it Live
The problem
We were helping organizations build better human experiences. But the methodology itself was hard to appropriate. Not because it was complex — because it had no home.
Coaches and teams had the knowledge. They didn't have the structure to make it theirs. Every project started with the same blank page. Every new team member rebuilt the same mental models from scratch.
The real challenge wasn't documentation. It was autonomy — giving people a framework solid enough to rely on, flexible enough to fit their actual work, and integrated enough to survive contact with a real project schedule.
Today
The platform is live in production. Teams onboard the methodology without a coach in the room. Activities are structured but not rigid — they adapt to the project, not the other way around. The framework holds across different profiles, different schedules, different levels of methodology maturity.
What changed: people stopped asking "what do we do next?" and started making that call themselves. Less friction, more flow. The kind of shift that's hard to design for — and obvious when it happens.
There's still ground to cover. But the foundation is there, and so is the intent: make the methodology feel like a natural part of how people work, not an extra layer on top of it.
From blank canvas to delivery, faster
The core design challenge wasn't building features. It was making a complex methodology feel effortless to use mid-project.
A team in the middle of an ideation sprint doesn't want to stop and read documentation. They need the right activity at the right moment, assembled into a workplan that reflects where they actually are — not a generic template that forces them into a process that doesn't fit.
The Plan Builder was designed around this tension. A visual, drag-and-drop canvas where teams compose their own project arc from structured methodological activities — seeing the full shape of a project at a glance, adapting it as the work evolves. Not a rigid framework. A living structure.
The AI assistant sits inside that workspace, context-aware, trained on the method. When a team hits a decision point, it doesn't redirect them to a knowledge base. It meets them where they are.
−54%
time to project delivery
57
structured activities, ready to use
06
project phases, fully integrated
97
Lighthouse score
WHAT THE FIELD CHANGED
- The first Plan Builder gave teams complete freedom from day one. Too much open space created paralysis, not creativity. Starter templates weren't in scope — real usage made them essential.
- Progressive activity discovery replaced the full catalogue view. Exposing 57 activities at once overwhelmed teams mid-project. Surfacing them by phase, at the right moment, changed how teams engaged with the method entirely.
- The AI assistant revealed how much strategic knowledge had never been formalised. Building it forced the kind of documentation that makes a methodology truly transferable.