What We Shipped This Week
Requirements Style (Beta!) - You can now teach Glossa what a good requirement looks like to you. Bullet points or long sentences? Heavy focus on the "why" or none at all? It's the style, format, and level of detail - your way. This is in beta, so expect more tweaking to come.
Faster requirements review - You told us you want to scroll through your requirements list more easily and spend less time reviewing them. So: we added an "expand all" button on the requirements list view, and bumped the default to 100 requirements per page. Now you can glance through them all at once, rather than clicking into each one. Works especially well with Requirements Style if you've trained Glossa toward shorter requirements - super scannable!
Total Active Requirements card - This new card excludes Canceled, Deferred, and Merged requirements, so the number reflects your real current scope.
Left Nav makeover - Clients, Systems, and Requirements Style now live together in a single Settings menu for the org. Tidier!
What's Coming Next
Discovery Questions - A library of questions to ask during discovery that dynamically updates with project context, so you don't miss anything. We're still shaping this one and would love beta testers - reply back if you're interested!
Propel '26 Recap
I presented at Propel26 on Wednesday. The talk was about how business outcomes tend to disappear in the handoff from sales to delivery; they get translated into solutions in the SOW, and the delivery team just builds to the SOW. We never come back to the original pain points and confirm we’re solving them! Glossa's new Business Outcomes feature fixes that 🎉 I'll share the recording from Propel as soon as it's available.