
New feature: Healthcheck Rule Configuration
We’ve just dropped an improvement to the Health Checks capability: Rule Configuration!
This article dives into the 3 core ingredients that enable a team to deliver at a high level of performance.
We’ll get into the weeds on each one, but in summary, they are:
Let’s dive into each one of these to understand why they are important in the context of a team.
Like individual identity, team identity can be a powerful driver of distinction, purpose and pride.
One important distinction with a lot of utility is what a team does and does not do. A team that is clear on this will spend less time deliberating on all the things that it could do in favour of pointed discusions on what it will do.
A team with an important purpose has no interest in getting bogged down in discussions about doing if it comes at the expense of actually doing. The opportunity cost is too high, the outcome too important not to be taking meaningful steps towards it.
Pride comes from making that progress, seeing the outcomes of the work, seeing that rate of progress grow, the quality of the outcome improve. Pride in themselves, what they’ve been able to accomplish together. A team that slays together, stays together.
Curating a team’s identity ideally starts at its inception. But given it’s not always possible, the next best thing is to rebuild the team around an identity that is the best compromise of what is needed and who you have.
A tool, even a bad one, is a force-multiplier; an object of leverage. The best tools offer the highest leverage.
A tool that does not create mechanical-advantage is either broken, or it is not a tool at all. Continuing to use broken tool almost always costs more than replacing with one that works. Using a not-tool is even more expensive again.
A team with mastery of its tools inspects them often, maintains them as required, trains with them to keep their skills sharp, and replaces them when they fail or degrade. They also don’t cart around any more than is necessary to do what is needed.
A high-performing team can explain exactly how it knows it is high-performing.
They can tell you which metrics they improved on from last month, and by how much. They can also tell you why of all the metrics available, why the three they’ve chosen to focus on are important.
They’ll be able to describe the changes they made to bring about those changes, as well as the things they tried that didn’t work.
You can ask anyone in the team and they’ll all give you the same story.
Thanks for indulging me with the above. So what are some practical things we can do?
Here’s some things I’ve found consistent success with the teams I have built, run and been a part of.
We’ve barely scratched the surface on this stuff. Please let me know if you’d love to read in more detail on any of the topics I’ve touched on in more detail.
For now, the key takeaways are:
Photo by Headway
We’ve just dropped an improvement to the Health Checks capability: Rule Configuration!
If you’ve ever used the default Timeline view in a Jira board, you’ll know that it is rather limited in what you can do with it.
The first release of TicketCoach is available now with the first feature to drop: Issue Health-checks