Happy Friday!
I’ve talked to many people about workflow diagrams, and the universal consensus is: they’re immensely useful, but really annoying to create:
Some projects would benefit from diagrams, but the project doesn’t have enough hours
Some BAs create them for every project as part of the standard process, but it’s time-consuming
Basically, no one said: workflow diagrams are useless. Or, I love creating workflow diagrams from scratch.
So we’ve automated it! Now, Glossa reviews all of your project context - requirements, user stories, and files - and finds the key workflows.
It shows you what it thinks those workflows are, including how they start, what people and systems are involved, and how they end.
It shows you pieces that it expected to find as part of the workflow, but that are still missing.
And then, it generates a visual diagram for each workflow, with swimlanes, decisions, and actions. Plus, each step is fully traceable back to its sources.
My hope is that you use Workflows live with clients. Share your screen, walk through the flow, and edit it together. It’s so much easier to review a visual than to read through a list of requirements - and you can work together to evolve it until it’s perfect (just describe what should change and click Update - the visual refreshes immediately).
Once your working session’s complete, Glossa will save all the changes you made and write them back to existing requirements, so you don’t have to keep track of what was changed and update it later. All of the changes cascade automatically (after you review and have the option to edit).
This feature has been a long time coming - thank you very, very much to the folks who gave feedback along the way (looking at you Diamond, Austin, Patrick, David, Bryan, and Sarah!). Try it out - I can’t wait to hear what you think.
What We Shipped This Week & What's Coming Next
This week:
Workflow diagrams - you'll find Workflows in the sidebar now. You can merge duplicate workflows, filter runs by status, and get rid of workflows you don’t need.
Capabilities connect to requirements - requirements listed under a capability are clickable, and there's a new "open in requirements table" action so you don't have to build filters by hand.
Jira site switching - if you use multiple Jira sites, it’s now simpler to switch between them, so Glossa info can flow to the right place more easily.
Coming next:
Workflow diagram polish - based on your feedback: do you need to export to Lucid? Change colors and shapes? Edit the diagram directly instead of describing it? Other things I haven’t thought of yet..?
UI/UX improvements - the UX team at Minimal has been working hard to make the overall experience better - more to come here soon!
Weekend Reading
A couple weeks ago, I talked about some of my Dreamforce takeaways. I ended that note by promising more thinking on AI Native Services in tech implementations, especially in the Salesforce ecosystem. So - (I hear it is “un-cool” to link to your own LinkedIn posts, and so to the haters, I say WATCH ME) - Here’s my summary of what I’ve been hearing in the market related to AI-first tech implementation companies. Would love to hear if this resonates with what you’re seeing too.
As always, don't hesitate to reach out - you know I love chatting all things SIs, services, Salesforce, AI, etc etc. Have a great weekend!
- Ali