Dependency Warnings
Jon Darbyshire
Hello Garrett Clawson! I have a few more questions for you:
- What specific scenarios or workflows in SmartSuite would benefit most from a dependency warning feature?
- How would you prioritize the importance of this feature compared to other potential improvements in SmartSuite?
- Are there any specific types of tasks or projects where you find dependency warnings particularly useful?
Garrett Clawson
Hey Jon Darbyshire!
What specific scenarios or workflows in SmartSuite would benefit most from a dependency warning feature?
Dependency warnings would be a huge help in workflows where tasks depend on client input or approvals. For example, in our Program Accelerator, clients need to complete surveys and provide feedback on deliverables before we can finalize them. A warning would help me and members of my team avoid moving too quickly or skipping important steps (especially team members who are newer to SmartSuite and could use some additional guardrails).
Other examples include:
- Grant writing: We can’t submit a grant until the client sends key financial data or signs off on the narrative.
- Strategic planning: We need to collect and finalize client feedback before we move forward with the next phases.
- Team collaboration: When tasks are split between our team and clients, dependency warnings keep everyone on the same page and prevent bottlenecks.
I’d say this feature is important, but I’d prioritize other enhancements, like AI summarization tools or similar time-saving functionalities, slightly higher. AI summarization has been surprisingly helpful for me in other tools like ClickUp and Notion and definitely made it easier to stay on top of client communications and project updates.