Best Practices Guide

Get the most out of Status Hero with these simple tips

We assembled this Best Practices Guide so you and your team can get the most out of Status Hero. It's based on decades of combined software delivery experience plus lessons learned from the thousands of teams using Status Hero every day.

Use these tips to connect with your teammates and build trust so you can confidently focus and deliver, together. 

Daily Goals, Not Tasks

Avoid listing small tasks in Status Hero. (Status Hero can pull in data from Jira, Asana, or Github issues anyway.)

Instead of tasks, think in terms of goals. Goals have the end product in mind. They define meaningful progress for your team and project. They also are the most effective way to communicate to others what you're working towards, increasing trust and delivery confidence.

Most knowledge workers should only have one or two concrete goals a day.

Example Goals ๐Ÿ‘
- Outline devops guide with Bob
- Fix the reporting bug
- Speed up builds by 10%

Example Tasks ๐Ÿ‘Ž
- Meet with Bob at 1PM
- Update reporting ticket #209
- Work on CI configuration

Longer-term Goals and OKRs 

Track longer-term goals or OKRs in Status Hero to weave context & vision into your team's daily routine. Collect updates from goal owners on a regular schedule that keeps everyone in the loop. Confidence and progress let you know at a glance where goals stand, and rich, longform updates create space for sharing deeper context, successes, and lessons learned. Learn the best practices for longer-term goals. 

Brief Check-ins

You need to put some thought into your check-ins, but each update shouldn't take more than two minutes.

Communicate just enough information to keep your team apprised of your progress.

To help you complete your update quickly, Status Hero will show you your goals from your previous check-in.

Write the performance tests for the reporting feature.

I was thinking Iโ€™d merge all of the overnight commits from Grace and
Steve. That reminds me, does anyone have a power strip I could borrow?
Mine is a little frayed. Anyhow if I donโ€™t get interrupted by the UPS
guy again. I'll be able to work on ticket #A7204FF634.

Use โ€œBlockersโ€ Wisely

"Blockers" are issues that 1) prevent you from moving forward and 2) require someone other than yourself to fix.

Only fill in blockers when you want someone else to intervene on your behalf.

Need @deborah to complete the security audit before I can deploy.

Feeling a little frazzled today from staying up too late last night.

@Mentions for Attention

When you @mention a teammate in a Status Hero update, they are immediately notified. So make sure you want their attention when you @mention them in your check-in.

Pushing the last bit of the search functionality to stage today. May need @ben
to help me address merge conflicts.

Work on search functionality. Chat with @ben later.


Comments and "Reactions"
๐Ÿ‘ ๐Ÿ‘Ž ๐Ÿ˜„ ๐Ÿ˜• โค๏ธ ๐ŸŽ‰

Like @mentions, when you "react" or comment on a check-in, the author and anyone else who has commented will be notified.

Make sure the communication is meaningful. Reactions are quicker than comments.

Let me know if you need help with the OAuth stubs!

Oof. The Cobb salad I had at lunch isn't sitting too well ๐Ÿฅ—


Use #hashtags to apply a category or area of work to your check-in.

Later on, you and your team can search check-ins by #hashtag to drill down into relevant updates.

Get the demo account prepped for the #sales webinar with prospects. 

Modularize all of the scripts in the dashboard #timeconsuming #mighttakeawhile


Supercharge your check-ins by connecting Status Hero to tools like Jira and Github for a full picture of what your team is working on. Use the Activity and Insights pages to view a live stream of activity and see trends over time. 

Take a Vacation

If you've got a planned vacation coming up, block off the dates in your settings. That way you won't be nagged to check in.

If you are the manager of your team, you can also set up team-wide holidays in the team settings.

Add Observers

Team administrators can set up certain team members as "observers." Observers receive summary reports and have access to the status dashboard. They are not prompted to check in.

This is useful for people who support your team (e.g. operations or security groups) and for providing stakeholders with automated updates.

10 or Less

We recommend splitting up larger teams into ones of approx. 10 people or less. Otherwise, teammates get overloaded with everyone else's check-ins.

In Status Hero, people can belong to multiple teams, or check in into one team and act as an observer in another.