Course 4.3 · Curriculum 2026.1
The seven design gates, and shipping systems instead of dashboards
Seven gates between a request and a shipped system. Understand the real operation, model it, design one surface, simplify, confirm, build in slices, verify.
- Estimated effort
- 4 hr
- Lessons
- 34
- Modules
- 6
- Material
- 4 hr
Estimated effort is the sum of the lesson and lab times in the course outline, for this version of the course.
This course is planned and not on sale. The curriculum below is the plan, and it may change before the course opens.
See the courses on sale01What you will learn
7 capabilities, stated as things you can do
Each one is what you should be able to do at the end, not what the course covers. If an outcome is not testable, it is not an outcome.
- Run a discovery conversation that surfaces the operation rather than the feature request.
- Model an operation before designing any screen for it.
- Design one surface rather than three, and defend the consolidation.
- Simplify by removal, and treat an addition as the expensive option.
- Confirm the design with the person who will use it, before building.
- Build in verified slices, so a partial delivery is still usable.
- Apply the seventh gate, which is course 4.2 in one sentence.
02Curriculum
6 modules, 34 lessons
Every lesson shows its length and its type, from the course outline.
6 modules · 34 lessons · 4 hr of material
The failure mode the seven gates exist to prevent: shipping a presentation of facts instead of a system that matches how a department actually operates.
- VideoThe failure mode: a presentation of facts instead of a systemPreview8 min
- VideoThe one-line test: what to do next in their job today7 min
- VideoIf it only shows facts, it is wrong6 min
- ReadingFive to six systems, one morning, and the cost of not consolidatingField technicians checked 5 to 6 different systems every morning before this was fixed.5 min
- LabLab: run the one-line test against a screen you already shipped10 min
- QuizCheck: the failure mode8 min
Gate one. The org’s own schema is a description of yesterday’s decisions, not of the operation someone runs today.
- VideoGate one: understand the real operationPreview7 min
- VideoThe discovery conversation, and the questions that work7 min
- VideoListening for the operation underneath the feature request6 min
- ReadingWhat a schema-first read misses every time5 min
- LabLab: interview a real user about a process you do not run12 min
- QuizCheck: understanding the operation8 min
Gate two. Entities, lifecycle, people and cadence, drawn before anyone opens a design tool.
- VideoGate two: model it before designing a screen7 min
- VideoEntities and their lifecycle, drawn before anything else6 min
- VideoThe people in the process, and the cadence they run on6 min
- ReadingModelling notation that does not need a tool to read5 min
- LabLab: model an operation from a transcript11 min
- QuizCheck: modelling the operation8 min
Gates three and four. One consolidated surface, and simplification treated as the harder, more valuable option.
- VideoGate three: design one surface, not threeField technicians went from checking five or six systems each morning to one. That consolidation was the product, not a feature of it.7 min
- VideoField technicians and five systems: what one surface replaced7 min
- VideoGate four: simplify, and treat addition as expensive6 min
- VideoKilling three dead surfaces in favour of one6 min
- ReadingRemoval as the default answer to a feature request5 min
- LabLab: cut a screen down to what a user needs today9 min
Gate five. A design confirmed with the person who will use it costs an afternoon. An unconfirmed one costs a rebuild.
- VideoGate five: confirm with the person who will use it7 min
- VideoWhat a confirmation conversation has to produce6 min
- ReadingThe design that looked right and was wrong in one meeting5 min
- LabLab: run a confirmation pass on a mocked-up screen8 min
- QuizCheck: designing and confirming8 min
Gates six and seven. Verified slices, then the done rule, which is the only gate an agent may not close on its own.
- VideoGate six: build in verified slices7 min
- VideoGate seven: the done rule, restated6 min
- ReadingDefinition of done: it has to have simplified something5 min
- LabLab: run all seven gates on one small request8 min
- QuizCheck: the seven gates8 min
04Before you start
What you need first
Assumed knowledge and setup
- Course 4.2. The seventh gate is that course.
- No coding required. This is the method, not the implementation.
- Useful for consultants and product owners as well as developers.
Before this course
05Who teaches it
Turni Saha
AI Adoption Lead, PMP
ShareCo Academy, and AI adoption for teams that are not technical.
Project Management Professional, issued 2024
06Reviews
No learner reviews yet
This course has not been taken by enough people to publish an honest rating, and we will not print invented quotes on a page that sells verification discipline. Here is what we can evidence instead.
- Assessment
- Lesson checks onlyThis course carries lesson checks and issues no certificate.
- Curriculum version
- 2026.1You enrol into a version. Content changes do not move you mid-course, and your required-lesson count is snapshotted at enrollment.
- Refunds
- 14 daysAn individual purchase can be refunded within 14 days if you have completed less than 20% of the lessons. Team seats are refundable before they are assigned. From the Academy terms.
Start 4.3
This course is in development and not yet open for enrolment. The courses open now are listed in the catalogue.
- 4 hr estimated effort, labs included
- A ShareCo certificate is not a Salesforce certification