๐ŸŒ Public

Claude Design: Where Can and Should Collide

Put your audience's needs ahead of your desire to show of cool AI-generated infographics.
3-min read
SHARE
Claude Design: Where Can and Should Collide
Image Source: Google Gemini/Nano Banana via Claude Code

All prescriptive nonfiction titles should contain clear, professional visuals. The right charts, graphs, and tables don't just give readers' eyes a break from endless text blocks. They also prove that the authors have done their research. Think of them as credibility steroids.

My 2022 release Project Management in the Hybrid Workplace is no exception to this rule. One of many its figures compares two popular but contrasting software development methods: Waterfall and Agile.

Figure From Project Management in the Hybrid Workplace | Click on the image to enlarge it.

Is this representation glamorous? Hell no, but it effectively serves its purpose.

AI Experiments

On a sleepy Tuesday afternoon, I asked the revamped Claude Design to create a visually pleasing infographic based on that table using my website's palette.

I'm curious to see if you can create an interesting infographic based on this table. Use the colors on https://www.philsimon.com.

Five minutes later, voilร !

Two Ways to Build Things

Waterfall vs. Agile

Ten dimensions that separate a plan carved in stone from a plan that keeps changing.
Waterfall
One step at a time. No going back.
VS
Agile
Small loops. Each one improves the last.
Sequential, fixed
Approach
Incremental, continuous
Large, specialized
Team
Small, cross-functional
โ€œWe can control everything.โ€
Mindset
โ€œWe canโ€™t control anything. Letโ€™s not even try.โ€
Long-term
Planning
Short-term
Fixed business requirements
Building Blocks
Flexible, constantly evolving user stories
Absolute (โ€œ4.25 hours to mow Jerryโ€™s lawnโ€)
Estimates
Relative (โ€œElaineโ€™s lawn is bigger than Jerryโ€™s, so longerโ€)
Once, when the project is complete
Feedback
Routinely, at the end of each sprint
Open
Loop Type
Closed
At the end of development, in a single phase
Testing
At the end of every sprint
Large, delivered at end of project
Batch
Small, delivered regularly
Phil Simon
philsimon.com

Note that Claude independently added the infographic's title and its one-sentence description. No prompts necessary. Ditto for the URL in the footer, although I can't copyright it.

Pro Tip: Limit Your Use of Cool Infographics

Claude's interpretation of my table works well, but only in the right contexts. Viewing online is one of them. For two reasons, though, I would never include it if I were writing Project Management in the Hybrid Workplace today. First, there's the aforementioned copyright issue. Second, the infographic's relative complexity would make presenting it in a 5.5" x 8.5" book challengingโ€”and those numbers exclude margins. Brass tacks: most readers would struggle to digest it.

As always, remember your audience.

What about using it during a keynote or webinar?

Hard passโ€”largely for the same reasons. Speakers who present dense slides and tables often lose their audiences. (Case in point: the clueless presenter in this post.) Conference attendees are doing one of the following:

  1. Listening to the person on stage.
  2. Trying to absorb the content on the slide.
  3. As is frequently the case, neither.

Foolish are the souls who believe audience members are concurrently reading and listening.

Finding the Right Automation Tool
Sometimes a replacement does the same job of the former at a fraction of the price.

Simon Says

Design whatever you like using these newfangled tools, but remember your audience. Put simply:

Can โ‰  Should

AI doesn't change that simple heuristic one bit.

Before You Goโ€ฆ
If you'd like to support my writing efforts, I'd appreciate it.

TIP THE AUTHOR

Member discussion