[mattlane66]

The goal of what we are doing is not simply to offer tooling as a way to instrument a process but tooling to enable talent and improve their interactions with others and subsequently improve the products they ship with simple, delightful, and effective lightweight software tools for making software. We want to power product feature work. To do this, we are unbundling specific functional aspects from the following toolchain categories while ignoring a whole bunch in exchange for a much more practical creation environment: Collaborative design software like Figma. Project management like Jira. Online whiteboards like Miro. Group chat like Slack. Long-form word processors like Google Docs (or, e.g., Notion’s pages). Reimagined functions from slices of these types of tools are carefully integrated into specific parts of Kraftkit, rendering the use of these popular products either null or reached for a lot less often. As much as it might sound like it, we are NOT building an all-in-one workplace product. Those solutions tend to be a jack of all trades and master of none. Although getting everyone across functions and disciplines into one tool to do a majority of their work sounds like a boon for the organization, it is, however, not possible or ideal. You’ll end up with either a bloated and complex interface, infrastructure, and company or a product that addresses only a few functions well, leaving most others in a less-than-ideal state, bumming people out who have to use it or pushing them to buy more tools than needed that are less than ideal.