Complete curriculum
Learn by building one trustworthy product.
Twenty days move from public need to client handover. Every lesson ends with observable evidence—not merely content consumed.
Phase 1
Discover
Understand the people, public need and product boundary.
Meet the problem
Explain Nisa’s six parts and the rule: Nisa informs; the NIS Board determines.
Design for real people
Create a user journey and wireframe that separates general information from a personal case.
Define the first journey
Agree on one public need, its source and the evidence that will prove the journey works.
Phase 2
Design
Turn evidence and user needs into a safe product plan.
Phase 3
Build
Create Nisa’s first working, explainable path.
Build from reviewed evidence
Return one useful answer from a reviewed record and stop personal cases before search.
Engineer the conversation
Produce a prompt and flow map another student can review against explicit rules.
Integrate AI safely
Demonstrate an AI-assisted response that remains grounded, limited and explainable.
Phase 4
Trust
Prove where answers came from and how unsafe cases stop.
Phase 5
Integrate
Join useful capabilities into one coherent experience.
Read documents responsibly
Add a document-reading path with file, source and failure boundaries.
Make Nisa easier to use
Add one accessible interaction that preserves the same typed answer contract.
Guide the next step
Help a new user complete a public-information journey without facilitator explanation.
Handle difficult journeys
Help the user move forward without collecting personal information or promising an outcome.
Demonstrate and listen
Show the integrated product, capture evidence and avoid invisible scope changes.
Phase 6
Showcase
Refine, confirm, harden and hand over the product.
Refine from evidence
Improve the highest-value weakness without destabilising the product.
Confirm facts and tone
Separate confirmed content from review-pending and unresolved material.
Harden every state
Prove Nisa remains useful and safe when inputs, dependencies or assumptions fail.
Prepare the handover
Create a handover package someone outside the team can understand and operate.
Show the product honestly
Demonstrate value, trust boundaries, evidence and team understanding.