Miro

A board is easy to run and hard to read a week later. Your assistant can find the board, page through every item on it, pull the contents of a specific frame, and list the tags in use, then write back what is on it in sentences. The useful part is not the sticky count. It is which frame filled up, which one stayed empty, and which ideas got repeated in three different words by three different people.

What you end up with. A written account of the board by frame, including the themes that repeat and the sections nobody wrote in.

Start with it bringing you the information and you deciding.

Never without. Read it as what got written down, not as what the room decided. The loudest idea and the most stickies are frequently different things, and the board records neither the discussion nor who conceded.

Built on: Get Boards V2 / Get Specific Board / Get Board Items / Get Items Within Frame / List Board Tags

It can list the members of a board with their roles, look up any one of them, and pull the board's own metadata including its team, owner, and sharing policy. Boards outlive the projects they were made for, and this is the fastest way to find the client-facing board that a contractor from last spring can still edit. Nothing changes by asking.

What you end up with. A per-board list of who holds which role, next to the board's sharing policy, so the ones that should be closed are visible.

Start with it bringing you the information and you deciding.

Never without. Miro's own note on this is worth keeping: the result is scoped to the permissions of the account you connected, so members and boards that account cannot see simply will not appear. An empty result is not proof of an empty board.

Built on: Get Board Members / Get Specific Board Member / Get Specific Board / Get Organization Context

Yes, and tagging is the version that survives. It can read every item on the board, see which tags already exist and which are attached to what, create the new tags a theme needs, and attach them to the individual stickies. The original wording stays exactly where the person wrote it, which matters when you go back to argue about what somebody meant.

What you end up with. The same board, with each sticky tagged by theme, so a frame can be filtered instead of reread.

Start with it doing the work and checking with you.

Never without. Approve the theme names before anything gets attached. Miro allows eight tags on a card or sticky note, so a model that invents a tag per nuance will hit that ceiling and start making choices about which theme to drop.

Built on: Get Board Items / Get Item Tags / List Board Tags / Create Tag / Attach Tag To Item / Remove Tag From Item

It can create the board with its name and description, lay in the frames that hold each section, and fill them with the prompt text, the instructions, and the starter stickies. Bulk creation puts up to 20 items on in one pass, which covers most agendas. The half hour of building a template at 8am is the part of a workshop nobody enjoys and the part that is fully described in advance.

What you end up with. A named board with its sections framed, labeled, and prompted, ready for people to write on.

Start with it doing the work and checking with you.

Never without. Set the sharing policy deliberately rather than accepting whatever the create call defaults to. A workshop board often ends up holding client names and unfinished thinking, and the permissions it was born with are the ones it will still have in a year.

Built on: Create Board / Create Frame Item / Create Items in Bulk / Create Sticky Note Item / Create Text Item

Describe the steps out loud and it can build them. It creates the shapes, positions them, and draws the connectors between them, which Miro requires to attach to two existing items rather than float loose. It can read the board back afterward to check what landed. This is the most reliable way to find out that a process you can describe fluently has two steps nobody owns.

What you end up with. A flowchart on the board with each step as a shape and each handoff as a connector, ready to be corrected by the people in it.

Start with it doing the work and checking with you.

Never without. Treat the first draft as a transcript of what you said, not as the process. It will render your description faithfully, including the steps you skipped because they were obvious to you.

Built on: Create Shape Item / Create Connector / Create Items in Bulk / Update Item Position or Parent / Get Board Items

It can read the items inside one frame, create cards carrying a title, description, due date, and assignee, update those cards as owners get settled, and tag them so the follow-ups are filterable later. The gap this closes is the familiar one where a retro produces twenty honest observations and no named owner for any of them.

What you end up with. A set of cards on the board, each with an owner and a date, traceable back to the sticky it came from.

Start with it doing the work and checking with you.

Never without. Never let it assign a person who was not in the session or who has not agreed. An assignee field filled in by an assistant looks identical to one a person volunteered for, and only one of those gets done.

Built on: Get Items Within Frame / Create Card Item / Update Card Item / Attach Tag To Item

It can page through the board, list what is on it, and delete items individually or by type, including stickies, shapes, text, and whole frames. Run it in two moves. Have it list exactly what matches your rule, read that list yourself, then approve deletion of that specific set. Miro's connector also warns to refetch items before a bulk operation, because item IDs go stale.

What you end up with. A board cleared of the old session's content, and a saved list of every item that was removed.

Start with it doing the work and checking with you.

Never without. Never approve a deletion described only as a rule, and treat deleting a frame as a decision about everything inside it rather than about the frame. There is no undo through the connection, so export or duplicate the board first if any of it is the only copy of a client's thinking.

Built on: Get Board Items / Get Items Within Frame / Delete Item / Delete Sticky Note Item / Delete Frame Item

It can read who is already on the board, invite people by email with a named role of viewer, commenter, editor, coowner, or owner, up to twenty per call, and change the role of someone already there. The role is the entire decision. Commenter and editor look similar in the invitation and are not similar on a board holding your working notes.

What you end up with. The right people invited at the right role, and a before-and-after list of board membership.

Start with it doing the work and checking with you.

Never without. Confirm the exact email addresses and the role for each one before it sends. The invitation email goes out immediately and cannot be recalled, so a typo that lands on the wrong domain is a disclosure, not a mistake you can fix by removing the member afterward.

Built on: Get Board Members / Share Board / Update Board Member