Appreciate the feedback! Nailing landing page copy is tough.
So you'd like to see something along the lines of "in Jira you'd do it like XYZ, in Kitemaker it'd look like ABC"?
So you'd like to see something along the lines of "in Jira you'd do it like XYZ, in Kitemaker it'd look like ABC"?
We should be focusing on what we plan to deliver to our users, regardless of the size. This is at the center of “outcome” before “output”
What I'm struggling with is seeing exactly how tracking a huge, "fluffy" outcome would be an improvement. For example, at my work we recently got a fairly big customer. As part of that, we will need to integrate with about 30 of their systems as well as implement a new API for them to send data to us.
Reading what you've written naively, it seems to me we should have a single "Integrate customer Foo" task to track. Without further details, I struggle to figure out to what degree this would be an improvement to what we're currently doing, which is using JIRA issues for high-level stuff like "integrate with invoicing system A", with a bunch of sub-issues for the details.
It could very well be we're missing out on something amazing, but without any concrete examples to compare to what we're doing, it's hard to determine. At least for me.