Best Of

Terrific post @DavidChurchman.

Domo’s competitive advantage is making the data-to-dashboard workflow simple and accessible. Strategies that reinforce that strength will continue to add value; those that pull focus away from it risk diluting what makes Domo effective.

I agree that continued investment in the foundational layer—cards, data modeling, and overall usability—is critical. Personally, I’m not looking to use Domo for building workflows or writing code. If I need that, I can use tools like Claude or Cursor directly. It’s also worth considering the added cost implications when similar capabilities exist outside the platform.

It feels like some of the current direction is being influenced by executive demand to highlight how AI is being used, rather than how data is being effectively leveraged. In practice, I still see challenges with AI reliably handling even relatively simple data relationships, like joins across a few tables. That can lead to impressive demos, but inconsistent results in real-world use.

With that in mind—and acknowledging that some of these may already be in development or beta—here are a few suggestions focused on strengthening the core experience:

Cohort / Retention Card (simplified)
• A card that shows how groups of users behave over time after they start

Example:
Group users by when they signed up (e.g., January, February, March), then track what percentage of each group returns in later weeks or months

Funnel / Conversion Card (simplified)
• A card that shows how people move through steps in a process—and where they drop off

Example (website flow):
Visited site → Signed up → Made a purchase

What you’d see:
Step 1: 10,000 users
Step 2: 4,000 users (40% conversion)
Step 3: 1,000 users (25% conversion from step 2)

Time Comparison Card (Smart)
• Automatically compares WoW, MoM, and YoY performance
• Includes % change and clear visual indicators

Variance / Waterfall Enhancements
• More robust variance analysis (plan vs. actual with contributing drivers)
• Moves beyond basic waterfall charts into clearer financial storytelling

Text / Narrative Card (non-AI)
• Rule-based summaries (not generative AI)

Example:
“Revenue increased 12% vs last month, driven by X”

Parameterized Cards
• A single card that can dynamically switch metrics or dimensions
• Reduces the need to duplicate multiple versions of the same card

Card-Level Versioning
• Track changes over time
• Ability to roll back when needed

Cross-Dataset Cards
• Blend data directly at the card level without requiring heavy ETL processes

Improved Debugging Tools
• Step-by-step data inspection
• Clearer error tracing and troubleshooting

Hey Aaron. Thanks for the call out! I just readjusted the accepted answer. You can totally accept your own answer. You won't get points for it but it will pin the answer to the top.

@DavidChurchman @ArborRose @MarkSnodgrass I also think that sometimes we are not good about putting things into release notes that impact cards. Sometimes it could be the small things like a setting on a donut. but sometimes other bigger things. I actually just reviewed some changes I requested to Flex Tables (had started this before this thread was a thought in your mind) as I use them a lot to show change over time for product metrics internally. Maybe like 5-6 changes to take it from sometimes useful to really awesome (sorting, some better labeling options). The engineer did mention there were a couple other new cards he was working on. And I would also call out that I think this ability to let a slicer filter set a variable is huge and game changing and I have been pushing for it for a while (https://www.domo.com/product/new-features/slicer-card-and-variable-linking, includes a video from yours truly explaining part of why I love it ).

Also, there is a balance between the "exec pushing for AI" narrative (which is true) and the reality of a new world. I have been doing a lot with Claude desktop chat and our early versions of MCP and it is game changing what I can do. Now at the end of it I want the option to create some old fashioned cards too if needed or maybe a few cards and one pro code component/brick with cards around them. And that is coming soon. Still some of that atomic unit of a card but letting AI make us faster and quicker.

I would also look at the new editing experience in app studio for cards. I was a hater at first. I liked my old analyzer (which yes maybe needed some refreshing). But editing in one canvas is super powerful and I am so glad we got this out to people now. https://www.domo.com/product/new-features/domo-bi-domopalooza-announcements

It is a balance always in the life of a product leader. Listen to customers, solve pain points, understand what is coming new, align with business priorities. that is the life I chose I suppose!