Team Commitment Management

The problem

A manager's team takes on work all day. A support lead agrees to call a customer back. An analyst says a report will be updated by Thursday. A new team member accepts a task in a chat thread. Some of this goes into a task tool. Much of it does not.

Managers find out about missed commitments from customers or other teams, and status meetings grow longer to make up for it. The manager asks each person what they are working on, each person gives an honest answer from memory, and the commitments nobody remembers stay invisible until someone outside the team complains.

Picture a support team on a busy Wednesday. Eight people have handled dozens of conversations since Monday. In several of them someone wrote "I will call you back tomorrow" or "I will check with engineering and come back to you". The ticket system shows the tickets. It does not show the promise inside the reply, or whether the call back happened by phone. The manager only learns about the missed call when the customer writes again, more annoyed than before.

The same pattern hides overload. One person quietly carries twice the commitments of anyone else. Nothing looks wrong in the task tool because most of those commitments were never entered. By the time the slips become visible, that person is already behind on several of them at once.

What GeniOS is designed to surface

In pilot, the aim is for a manager to receive intelligence about the team's commitments, drawn from email, calendar, chat and the business tools the team already uses. Each person on the team would see their own commitments; the manager would see the ones that need attention.

• Who committed to what. Commitments each person has made, with their dates, wherever they were made.
• Work near its date. Outstanding work close to its date with no sign of progress.
• Overload. People carrying more commitments than they can meet, raised before the slips start.
• Kept commitments. Commitments kept, closed on proof such as a sent reply, a logged call or an updated record.

As with all GeniOS intelligence, a person stays in charge: nothing is sent or changed until someone approves it. Each note ends with Delegate, Done, Later or Not relevant, so the manager can move a commitment to someone with more room in one step. For promises made across the whole company, see Commitment Tracking; for promises made to an upset customer, see Customer Escalation Tracking.

A worked example

Example at a generic company. Names, dates and numbers are made up to explain the idea.

A customer support manager at a software company leads a team of eight. On Monday, three people promise customers a call back within a day. By Wednesday one call has happened.

Nobody on the team is careless. One agent was pulled into a product incident on Tuesday. Another has been covering for a colleague on leave and is carrying almost twice the usual number of open conversations. The ticket system shows both customers as waiting on the customer, because the last message in each thread was the agent's promise.

Here is how it would look in pilot: the manager receives one note saying two promised call backs are overdue, one with a customer whose renewal is next month, and suggesting the senior agent take that call today. A second line points out that the agent covering for a colleague holds the most open commitments on the team this week. The manager delegates the renewal customer's call to the senior agent, moves three of the covering agent's open items to a colleague, and approves a short note to the second customer setting a new time. Both items close once the calls appear in the call log and the follow-up notes are recorded.

How teams use it day to day

Team Commitment Management is meant to replace the long status round with a short look at the few commitments that need the manager.

1. Each person checks their own list

   Every morning, team members see the commitments they have made that are due soon, wherever they made them.

2. The manager reads the exceptions

   The manager looks only at overdue commitments and at anyone carrying too many.

3. Rebalance early

   Delegate a commitment to someone with more room, or set a new date with Later, before the customer has to chase.

4. Close on proof

   Commitments close when the reply, call or record update appears, so nobody fills in a status report.

5. Use the weekly view in one-to-ones

   Bring the pattern of kept and missed commitments into one-to-ones as a workload conversation.

Where it applies

These are application areas where this use case can apply, not a list of current deployments. Our design partner work so far is in manufacturing, with Vaultex.

The use case applies to any team that makes many small promises: support and customer success teams promising call backs, sales teams promising proposals, operations teams promising dates and human resources teams promising answers to candidates and staff. It fits software companies, professional services firms, healthcare providers, education businesses and hospitality groups, where much of the work is promised in conversation.

• Domains: Operations, Customer Success & Support, Sales, Human Resources
• Industries: SaaS & Technology, Professional Services & Consulting, Healthcare, Education & EdTech, Hospitality & Travel
• Roles: Managers

Status

Pilot We are shaping this use case with design partners now, and it is not yet a finished part of the product. If this is a problem you have, talk to us about shaping it with us. Design partners help us decide how a team's commitments should be shown to each person and to their manager.