One model, from the market to the specification.
Kheel connects what you know about your market and your customers to what your product does and how it's built. Your AI assistant does much of the work in it with you, and you don't need to learn the structure first.
Kheel is in beta: all of it is here, and it's changing quickly. What's in the beta.
Room for every product you look after
Each product gets a space of its own, with a tree of domains to find your way around it. Its work moves through levels, each answering a different question: what's true of the domain whatever the software, what the product must do, and how it does it. Keeping them apart stops a guess about the solution passing for a fact about the domain, for you and for your assistant. Everything links to what it serves at the level above, so you can see what nothing serves yet. The areas below sit on these levels: the domain is the concept level, capabilities are the capability level and the specification is the design level, with the market beside them all.
- Concept
- Book an appointment, as patients need it done
- Capability
- UC4, what the portal does for them
- Design
- The booking flow that carries it out
Market
Track who else serves your customers. Keep a record of each competitor, compare them on the dimensions you care about, and note what each one means for your product.
- Competitors
- Other products, other firms, or the spreadsheet people use today. Who's behind each, how they're financed, what they offer and your read of what they mean for you.
- Moves and threats
- Log what competitors do, raise threats and close them, and see when a record has fallen behind.
- Dimensions
- Compare everyone on the measures that matter, your own offerings included.
- Segments, customers and personas
- Where you compete, the customers you go after, and the people you meet in each sale, marked as assumed until someone has checked with them.
“Who has moved since we last looked?”
“Which of our personas have we never checked with real people?”
Domain
Get the domain right first. Record the terms people use, the work they do and the rules that apply, independent of any software. A word that means two things here becomes two mistakes later, in the data, the screens and the code.
- Language
- Terms and the relationships between them, each defined once, with the other names people use for it.
- Jobs and outcomes
- What people are trying to get done, its steps, and how they judge each step done well.
- Domain rules
- What must hold in the domain, and where it varies, by jurisdiction or by kind of business.
“Do we use ‘client’ and ‘patient’ for the same thing?”
“Which steps of getting seen do patients find slowest?”
Capability
State what your product does. Describe what it does for its users without reference to screens, databases or APIs, precisely enough that each statement can be checked.
- Activities and tasks
- The work as your product shapes it, from the goals people pursue to the results they produce.
- Use cases and stories
- What each person achieves with the product in one sitting, and the commitments it makes to them.
- Business rules and constraints
- What the product enforces or calculates, stated once and applied wherever it's needed.
- Acceptance examples
- Concrete cases that show a story is met: a starting situation, an action and the result.
“Which stories have no acceptance example?”
“Which use cases apply the deposit rule?”
Specification
Specify how it's built. Record design decisions with their reasons, and the detail a developer or coding agent needs, each linked to the capability it delivers.
- Decisions
- What was decided, what else was considered, and what follows from it.
- Specifications
- The flows, records and checks that carry out each capability.
- Links between levels
- Each artefact links to the one it serves at the level above, so you can see a need that nothing in the product supports, or a feature that meets no need.
And user experience
Personas are already part of the market area, and the free mockup skills, which run on your own machine rather than in Kheel, let your AI draw screens, sections and dialogs from your own design system and lay out options to choose between. More tools for user experience are planned.
Try it with your own product
Start with a demo organisation full of example content and ask it the questions on this page, or set up your own. Free for three months while Kheel is in beta.