Last December, I was demoing AI tools for a real estate company — showing the team what was actually possible with the current generation of models.
At one point, I showed them what Gemini could do with their weekly project status reports. The owner of the business started immediately naming things: 30, 40 different ways he could use this across his properties and his team.
Here's what I showed him.
The Problem With Long Status Documents
This company sends project status updates every week. One document covering all active properties — what's on track, what's delayed, what needs a decision from leadership. Construction timelines, pending permits, budget flags, contractor notes. Fifteen-plus pages when you include everything.
The information is all there. It's accurate. It's detailed.
And most of the team skims it.
That's not a people problem. That's a format problem. When your status report is a long document, people have to read it linearly to find the part that affects them. Some will. Most will scan headings and stop when they find their section. A few won't open it until they have to answer a question.
The document works as an archive. As a communication tool — for getting your whole team aligned on status in real time — it's too slow.
What Happens When You Add a Visual
I took one of their status reports, fed it to Gemini with a prompt asking for a visual dashboard summary, and let the model render it.
What came back: one page. Every property listed. Status indicators — on track, delayed, decision needed. Key flags visible at a glance. The kind of layout you'd recognize immediately if you've seen a project management dashboard, but generated from a text document in about 30 seconds.
The reaction in the room was immediate. Everyone could take in the full picture at once. No hunting through pages. No skimming headers. Thirty seconds and the team had a shared understanding of where everything stood.
The owner started asking questions about which properties were flagged — not because he'd read the document, but because the visual made the flags obvious.
Why This Works
A long document and a visual communicate differently, and the difference matters.
A document says: “Here is all the information. Navigate it to find what you need.”
A visual says: “Here is the picture. Everything important is visible at once.”
Most status communications are designed for the person creating them — the person who needs to capture everything accurately. The format serves completeness. But the people receiving the update need something different. They need to orient quickly, identify what affects them, and move on.
The visual does that. The document doesn't.
What's interesting is that you don't have to choose between them. The document stays — it's the source of truth, the archive, the reference for anyone who needs detail. But you generate the visual from the document and distribute that instead. Recipients get the picture. They pull up the full doc if they need depth on a specific item.
How to Build This
The model I use for this kind of work is Nano Banana, which is Gemini's image generation model. It handles infographics, bento-grid layouts, status dashboards, sketch-note style visuals. You don't need a designer or design software — you describe what you want in a prompt and the model renders it.
For a project status visual, a prompt might look like:
“Create a visual dashboard summary of the following project status report. Include all properties as individual cards showing status (on track / delayed / needs decision), key upcoming milestones, and any flagged items. Use a clean, professional layout.”
Then paste the full document text. The model will interpret it and generate the layout.
The first version won't always be perfect. But you can iterate quickly — adjust the layout style, ask for different color coding, change what gets emphasized. A few iterations and you have something worth sending.
This works for real estate and construction, but it applies to any team sending long status updates. Product development teams with weekly sprint reviews. Operations teams with weekly reports. Project managers with multi-site coordination docs. Anywhere you have complex text-based updates that need to be quickly absorbed by multiple people.
The Broader Point
There's a version of AI productivity that's about making your own work faster — writing faster, researching faster, processing email faster. That's real and valuable.
But there's another version that's about making communication more effective. The status visual is in that second category. It doesn't save the person creating the update much time (though it saves them some). What it does is save everyone receiving the update significant time and cognitive effort.
That's a different kind of leverage. And it's one most teams haven't started using yet.
Thanh Pham is the founder of Asian Efficiency and an AI consultant based in Austin, TX. For more on using AI for team communication and project workflows, check out the 4-Day AI Sprint.
