Video, team, risks & kanban
The four artifacts that close the set — an intro video to show what you built, a team tab for who does the work and how, a risk register for what can go wrong, and a kanban to track getting it done.
4 min read
Artifacts
In one line: with the deliverables made, what is left is showing it and doing it. The video (⌘9) plays your deck as an intro video or embeds an existing one; the kanban (⌘0) turns what happens next into cards. That is why they hold the last two places in the row.
Kanban
A planning board with columns like To-do, Doing, Done, where cards show progress at a glance.
Knowledge
⌘1Research
⌘2Interviews
Concept
⌘3Branding
⌘4Design
Spec
⌘5Model
Metrics
Proposal
⌘6Deck
⌘7Q&A
Prototype
⌘8Website
Video
⌘9Team
Risks
Kanban
⌘0Video and kanban close out the tab row.
Video (⌘9)
The video is an intro-video artifact with two modes.
Deck slideshow: plays your live deck as an auto-advancing slideshow with play, pause and seek — an intro video with no extra editing.
URL embed: paste a YouTube, Vimeo or MP4 link to embed an existing video inside the project.
You do not edit the video from scratch. If you already have a deck, play it as a slideshow; if you already have a video, just paste the link.
Kanban (⌘0)
The kanban is a board of columns and cards for planning and tracking the project. It is edited live with the team, so every move shows up instantly for everyone.
Like every other tab, these two can be driven by chat or edited directly, and saved with ⌘S.
To kick these off from chat, try saying:
Make tasks
“Turn this week's tasks into kanban cards.”
Do I have to edit the video myself?
No. Auto-play your deck as a slideshow, or just paste a YouTube, Vimeo or MP4 link.
Team
The team tab records who does the work and how the work runs: roles, cost, a RACI grid, and the working method chosen for this project — scrum, kanban, scrumban, waterfall, shape up.
A method will not save without the reason it was picked. "We are agile" is a mood, not a method — what gets stored is which condition of this project made that choice right.
Risks
The risks tab is a register written as cause → effect. Probability × impact scores each one onto a 5×5 exposure matrix, and mitigation (before) is kept separate from contingency (after).
The trigger — what you would actually see if the risk fired. Anything without one is collected into a warning at the top.
Residual score is what is left after mitigation. It can never exceed the inherent score, and if it does not drop, the row says so.
A risk that already happened leaves the matrix — what has occurred is no longer a probability.
Most risk tables stop at the mitigation. That is how a risk fires without anyone noticing. Write the trigger as something you could actually check in a weekly review.
Related articles
Still need help?
Reach our team and we’ll help you out.