Happy Friday-before-a-short-week!
What We Shipped This Week
Answers ↔ Requirements, both directions - We launched Discovery Questions last week, and with your early feedback (thank you!!), we've been iterating fast. Two big things this week:
Glossa now sources answers to your discovery questions directly from your files (meeting notes, docs, emails, etc), not just from requirements, which can sometimes be too concise and summarized to answer detailed questions.
And we're closing the loop the other way: those answers now tie back to requirements, so nothing you learned in discovery gets dropped.
What We’re Working On
We’re focused on quality of life improvements for the next couple of weeks. With our quickly growing user base (yay!) we’re hearing lots of small improvement requests that will make everything smoother to use, for everyone. A few areas we're planning to improve: categories, portal, acceptance criteria, and notifications. If you have opinions on any of these or how they could be better, reach out!
What's Coming Next
Client-Facing Discovery Questions: Imagine if, before kickoff, your client could upload a few of their own documents and answer some basic discovery questions directly. They get engaged early, and it gives you a head start - so you can focus on the gnarliest parts of discovery sooner rather than spending the first couple of sessions collecting rote info. Let me know if you’d like to be a design partner for this!
Diagram Creation: BAs build user flow diagrams by hand all the time. It's manual and slow, but worth doing, because diagrams are so useful in conversation - clients can spot issues and inaccuracies visually in a way they just can't from a list of requirements. We have ambitious plans for this big, big feature - let me know if you’d like to be a design partner here.
As always, if you have questions, feedback, or just want to chat about what I'm seeing in the market, you know how to reach me. Have a wonderful weekend!
- Ali