From Blank Page to Flowchart in Seconds — My Skip the Blank Page Month Journey

[#1]

A month worth going deeper

I've been using Rovo for nearly six months now creating pages, experimenting with whiteboards, exploring what it can do. But Skip the Blank Page Month pushed me to go further than my usual use cases and actually stress test it with structured, real-world scenarios.

Skip the Blank Page Month changed that.

How it started

Week by week the challenges built up naturally:

• Week 1 — Rob Hean's first look video showing Rovo creating whiteboards and databases from scratch. That's where it first clicked that this wasn't just a writing assistant.
• Week 2 — Prompting tips, real use cases from Atlassian teams across product, research, marketing. Seeing how different teams used the same approach for completely different workflows was eye-opening.
• Week 3 — The live hands-on workshop on March 19th with Rob Hean. You got your own Confluence demo site pre-populated with dummy data, and you followed along in real time — not watching someone else's screen, actually doing it yourself.

That workshop is where things got real.

What I tried

The scenario given was a "Mobile App Version 2.0 Requirements List" page that needed to be converted into something trackable and actionable. I ended up exploring a few different things with it.

1. Converting a page into a Database

First thing I tried was asking Rovo to turn the requirements page into a structured database. The prompt was straightforward — told it I was a project manager, linked the page, and asked it to build something I could actually track work in.

What came back was a fully structured database with columns for Requirement, User Story, Importance, Jira Issue and Status — all pulled directly from the page content. No manual setup, no column dragging, no formatting. Just described what I needed and it was there.

2. Editing and iterating on the fly

This is where it got interesting. Once the database was created I wanted to clean it up — the Notes column was cluttering the layout. So I just asked Rovo to remove it.

It didn't just delete the column. It updated every single view — All Requirements, High Priority Items, By Status — automatically. And then told me exactly what it changed and why. That level of transparency in the iteration was something I didn't expect and genuinely appreciated.

That moment changed how I think about using Rovo. You don't have to get it right on the first prompt. The back and forth is the feature.

3. Building a Whiteboard Flowchart from scratch

The one that impressed me most visually was asking Rovo to create a full process flowchart for a Laptop Request Workflow.

The prompt: "Create a Whiteboard Flowchart that maps out the process: Requesting the laptop, the approval branch (Approved/Denied), the IT setup phase, and the final security orientation."

What came out was a fully structured whiteboard — start and end points, decision diamonds, approved and denied branches, IT setup steps, security orientation flow, timeline, common issues, success criteria and key notes. All from one prompt.

What would've taken hours manually in Miro or Lucidchart, Rovo put together in seconds. And just like the database — when something needed adjusting, I just asked. No starting over, just iteration.

The framework that actually stuck

Out of everything covered this month, the one thing I'll keep using is TCREI:

• T — Task
• C — Context
• R — Rules
• E — Example
• I — Iteration

Simple enough to remember, powerful enough that you immediately want to go back and rewrite every vague prompt you've ever used.

The biggest shift wasn't learning the framework though — it was understanding that you don't have to nail the prompt on the first try. Iteration is built into the process. That takes the pressure off and makes the whole thing feel a lot more like a conversation than a command.

What surprised me most

The breakout room structure in the workshop. Each room got a different scenario so you couldn't just repeat what Rob already demoed — you had to actually think about how to prompt for YOUR use case. That's where TCREI went from a slide bullet point to something that genuinely makes sense in practice.

Also the community itself — reading everyone's comments and tips across the weekly posts genuinely added to the learning. Seeing how others approached the same prompts differently was as valuable as the content itself.

#Skiptheblankpage #CreatewithRovo