As much as I like developing software, I sort of wish these tools existed outside of the software use case. It seems like 80% of the concept can be repurposed for other types of team collaboration and I'm not sure how well that market is served
They do but it’s hard to gauge how widely, in part I think because folks doing those things are less likely to blog /post about it. But for example in a past role I set up Jira for a non-IT team in a national museum, and a colleague did the same to help a supermarket chain develop new products.
I love this comment. For example, I have yet to find a tool that helps teams manage worker leave (medical, parental, mental health, etc.). A way to quickly get a co-worker up-to-speed on your projects before you take leave; a place to document the calls, check-ins, etc. while you are out; and board to manage tasks upon your return.
We don't disagree and we've heard from non-technical managers and designers that Constructor has the potential to be simply "a better Trello for everyone". This is probably because despite being designed for software teams we try to serve all roles equally well, i.e. make sure we create an outstanding UX for the non-developers on those teams. Something we've seen happen at a lot of places is a "tool schism" where part of the team (design or PM) will cleave off and use Trello or Basecamp and leave the devs to Jira because they find it unusable, but the devs need their Jira for various good reasons. Constructor is designed to prevent tool schisms.
Your 80% observation is if anything an underestimate; there's almost nothing in Constructor that makes it dev-specific beyond the GitHub and devops integrations that are mostly absent if you don't activate them, and would be easy for us to make totally optional. This surprised us when we realized it, because we are quite devoted to serving software teams specifically.
