[qudat]

> On the other, a tool that's too open-ended may overwhelm users with options when they should really be focusing on dev.

Author here. I agree. A big concern is I build this flexible system and a user jumps in to use it and sees a blank screen. No story section, no sprint section, no epic section. They get bewildered and end up not using it. Do you have any other thoughts on how to combat users being overwhelmed by a blank screen? I could have templates that people could "load" that would set a project up like a traditional project mgmt solution would?

[Aalk4308]

Yeah, templates for "traditional" structures sounds reasonable. Or along the same lines, it might be sufficient to have purely illustrative versions of those setups ("here's how some teams have used this"), to get the idea across, even if they can't be "loaded" as a template.