A bit tangential, but I was surprised at how similar Kitemakers offering _sounded_ to Linear (https://linear.app/).
Could you elaborate a bit on that? I'm curious what you discovered in that regard.
And you can bundle those together like "A user should be able to cancel and return to the project screen from any step of the wizard." Alternately, you can separate things by teams like "An API exists to cancel the reservation in progress, releasing the underlying inventory" vs. "A user can cancel the reservation in progress using the API" vs. "Factor out cancel buttons into a UI abstraction" if you want people to be able to pick those up and show progress independently.
But fundamentally all this stems from an underlying plan, that flow chart from which all these stories flow. That plan is the epic. But that plan can't just be a frozen flow chart; it needs to be a living central repository of documentation, ideas, and mockups.
Ideally, you have few enough of these epics that you can maintain things in the tools they're meant to be in: a Clubhouse epic, for instance, could simply link to the top-level Notion table of contents for the planning process for that epic.
But if you're pulled in a billion different directions and have a massive feature surface, having this all in one place, alongside the chat related to that feature, with live references to the ongoing action items, would be incredible. Whether Kitemaker solves it or someone else, there's amazing work still ahead here.
There's no shortcut for organization and I doubt a tool will ever solve it all, but I think the combination of wiki+task manager+interactive chat is utterly begging for a (good) unified tool that makes it easy to document, chat, and work tickets in the same place. I imagine the end result wouldn't be automatic quality documentation, but more like an automated blog of what stuff your company is shipping. People wanting to catch up (for context, new teamates, etc) can kind of peruse recently completed features and pick up a ton of context, or search specific ones and build a good understanding of how it was implemented (and why). It seems it would lend itself naturally to a culture of documented, intentional communication, rather than the splattering of slack messages and random tickets I see so commonly. If anyone has interest in working on this, happy to join up. Its high on my list of "want to" side projects.
We definitely think it’s a huge market and it’s undeniable that products like clubhouse will keep having success. But for us, we’ve set out to build something that changes how teams think about these types of tools. That’s why we’re pushing to get the whole team engaged and really make use of the document-like aspect of Kitemaker (which teams tend to use a bit differently than stories in clubhouse). It’s early days still, but initial feedback has been really positive and quite a few teams are paying us already.
And now "Unable to log in. We were unable to parse the server response. This could be a networking issue, so please try again later."
Trying Kitemaker now and hoping the HN hug of death isn't approaching. First impressions: I appreciate the keyboard-shortcut-first UI.
I thought clubhouse was that audio chat thing, but it seems they don't own an actual domain name for their company.
It is, but project management Clubhouse [0] has been around far longer than audio chat Clubhouse.
I have had two truly delightful, joyous SaaS experiences in the last few years: ClickUp and Retool.
For example, you can flip major features on and off without even a hiccup (like Sprints or Subtasks). I just can't begin to imagine the architecture behind that capability.
It’s the first PM app I am actually recommending to people, and we tried so many. Every single one has been just a “lesser evil”.
I am in no way affiliated with ClickUp. I just hope they don’t overmonetize or something like that.