How to surface and solve team problems before they become crises

Every business has problems. The ones that hurt are the ones nobody mentioned until they were too big to ignore: the client who’d been unhappy for months, the hire who was struggling from week two, the process everyone worked around instead of fixing.

A challenge list makes problems normal to raise. It’s a shared, visible list of issues the team hasn’t solved yet, worked through in priority order every week. In Clarion these are challenges, and the operator’s job is to keep the list honest and keep the team working it.

Make raising a challenge easy

If raising a problem takes effort, people won’t. Clarion offers several quick routes:

• Quick add. Click Quick Add in the sidebar from any page, or use the Add button in a live sync. See quick add.
• From a metric. When a number is off target, Flag as challenge in the metric’s history creates a challenge with the current value and target filled in, assigned to the metric’s owner.
• From an action item. If an action item keeps slipping, Create challenge from its menu turns it into a discussion. The two stay linked.

Each challenge has a title, a description, a priority (high, medium or low), an owner and notes. It also shows how many days old it is, which turns out to be a useful nudge.

Tell the team plainly that raising a challenge isn’t complaining. A challenge that’s raised early is cheaper to solve than one that’s raised late.

Let the team decide the order

Before the meeting, everyone votes on the challenges they think matter most. One vote per person per challenge, and you can take your vote back. The list sorts pinned first, then escalated, then by votes, so by meeting time the order reflects what the team thinks, not who’s loudest.

Use pin sparingly, for the one issue that has to be discussed this week regardless of votes.

Solve them, don’t just discuss them

The Challenge Discussion step is the longest in the default sync agenda, at fifteen minutes. Use it to work the list from the top:

1. Name the real problem. The challenge as written is often a symptom. “Deliveries are late” might really be “we promise dates before we check stock.” Spend a minute getting to the cause.
2. Discuss briefly. Everyone says what they need to say, once.
3. Decide. Not “let’s think about it.” A decision, even if it’s “we’ll try X for two weeks.”
4. Capture the action items from the challenge’s own panel, each with an owner. That’s how the fix gets done.
5. Resolve it, and move to the next one.

If you get through two challenges in fifteen minutes, that’s a good meeting. If you get through none because the first one turned into a debate, the team needed a decision-maker in the room. Resolved challenges keep their resolution date and can be reopened if the problem comes back. Show Resolved brings them back into view.

Use escalation for what a team can’t solve alone

Some problems can’t be solved at team level. They need a budget decision, another department, or a call that only leadership can make. That’s what Escalate is for.

An escalated challenge is marked as escalated and sorts to the top of the list. On the Challenges page, leaders see a card for each team that reports to them, showing its open, escalated and high-priority challenges and the oldest of the most concerning ones. So an escalation is visible upward without anyone sending an email.

Escalation should be rare. If everything is escalated, nothing is, and the leadership team ends up solving problems the department should own. When the problem is solved, use Remove Escalation or resolve the challenge.

A weekly rhythm

• Any time: raise challenges as they come up. Don’t save them for the meeting.
• Before the sync: everyone votes. The facilitator checks the top few are clear enough to discuss.
• In the sync: work from the top. Decide, capture action items, resolve.
• After the sync: follow the action items, using keeping action items moving.
• Monthly: look for challenges more than thirty days old. Either solve them, escalate them, or admit they’re not real problems and resolve them.

Common mistakes

Discussing without deciding. The same challenge on the list three weeks running is a sign the team is talking, not solving.

Solving symptoms. If the same kind of challenge keeps coming back, the cause was never found.

Too many challenges. A list of fifty is a backlog, not a priority list. Merge duplicates and drop the ones nobody votes for.

Leaders raising everything. If only the boss raises challenges, the list reflects one view of the business. Ask the quietest person in the room what’s in their way.

Escalating to avoid a hard conversation. Escalation is for problems the team can’t solve, not ones it doesn’t want to.

The clicks are in raise a challenge and vote and escalate challenges. Where challenges fit in the meeting is covered in running the weekly sync.