Project Idea
Thoughts using the Action Items feature
Project Submitted By
@luisblancoach
Summary
During today's call I spent some time using the Action Items feature and a few UX observations came to mind. This isn't a feature request as much as an invitation to discuss how the list communicates priority and coordination.
Why should we build this?
The current list presents every action item with roughly the same visual weight, even though some tasks are foundational and unlock several downstream initiatives.
Making relationships like dependencies, blockers, and leverage more visible could help members prioritize work more effectively.
Some ideas:
- Surface Leverage (✦✦✦✧✧), not just Priority
- Show Dependencies and Blocked by
- Group related initiatives (Campaign, Content, Infrastructure)
- Reduce visual repetition with avatars, icons or previews
- Add filters like High Leverage, Needs Owner, or Waiting on Others
From a content perspective, I'd also consider grouping work into a few higher-level initiatives instead of presenting everything as a flat list:
- Campaign: outreach, KPIs, funding, recruitment
- Content: articles, YouTube, Reddit, educational content
- Infrastructure: crawler discovery, Portal discoverability, SEO / GEO / AEO
Anything else you'd like to add?
This isn't intended as a formal proposal—just a collection of observations after using the feature in a real meeting. I know is internal feature, but we can still improve it.
Curious to hear what others think.
Raid Party Skills Needed
Design
Frontend
Cost
N/A (discussion)
Project Idea
Thoughts using the Action Items feature
Project Submitted By
@luisblancoach
Summary
During today's call I spent some time using the Action Items feature and a few UX observations came to mind. This isn't a feature request as much as an invitation to discuss how the list communicates priority and coordination.
Why should we build this?
The current list presents every action item with roughly the same visual weight, even though some tasks are foundational and unlock several downstream initiatives.
Making relationships like dependencies, blockers, and leverage more visible could help members prioritize work more effectively.
Some ideas:
From a content perspective, I'd also consider grouping work into a few higher-level initiatives instead of presenting everything as a flat list:
Anything else you'd like to add?
This isn't intended as a formal proposal—just a collection of observations after using the feature in a real meeting. I know is internal feature, but we can still improve it.
Curious to hear what others think.
Raid Party Skills Needed
Design
Frontend
Cost
N/A (discussion)