How can I use Team Intelligence

Your Morning Brief arrives on weekday mornings, so the overnight and end-of-day responses are already summarised by the time you open it. Read it on your commute into the office, or over your daily coffee. You'll walk into your first meeting of the day already knowing what changed, instead of finding out at 11am from someone else.

leep prepares Actions based on your most recent and urgent Signals. They are suggestions, and you can mark them complete or add your own.

Before you commit to a date, a scope change, a hire or a supplier, spend 30 seconds in Ask.

You're in a meeting, someone asks something about your Team, and you don't have the detail. Open Ask on your phone and get the answer you need.

When a Signal is useful, acknowledge it so that your team know you're listening. Pick one of the four prefilled messages or write your own. It goes by email straight away to everyone who contributed to that Signal, whether that's one person or six, and it also shows on the confirmation page the next time they respond.

Instead of using 1:1's to catch up on what your direct report's been working on, what's blocking them, you can arrived fully briefed. Head to your team member's profile in leep to see their recent themes, signals, engagement and access their 1:1 Preparation which contains bullet point topics to cover. Use the time on areas that need a decision, a trade-off or coaching.

Use leep to provide weekly updates to your own leader, or contribute to management meetings. "Mentioned by four people this week" carries more weight than "there's some concern about".

Instead of chasing your team for commentary they already gave you, head to Ask, and type "What were the main themes from the Team in July, with the number of people who mentioned each? You receive themes, counts and quotes to include in your MBR.

If your Team talks to customers, they hear things all day that never reach anyone who could act on them. You can share front-line customer intelligence across the business in five minutes, with quotes attached.

Your team hear a competitor's name in a live deal or customer feedback weeks before it appears in a win/loss review.

Your salespeople hear about the product. Your support team hears about marketing. Once a month, pick the two or three Signals that belong to somebody else and pass them on yourself, with the quotes.

Support Headcount and budget requests with front-line evidence. Take verbatim quotes into the conversation. "Four people mentioned the same bottleneck in three weeks, here's what they said".

Pull the month's themes before the retro, send them round beforehand, then spend 20 minutes on decisions and outcomes instead of 60 minutes on remembering what actually happened.

Draw on a full quarter of front-line responses rather than reconstructing the quarter from memory and Slack scrollback.

Before you commit to next quarter's plan, check it against what your Team has been telling you all quarter. The blockers people mentioned in month one are usually still there in month three, and they are usually the reason the last plan slipped.

Before you lock next quarter's goals, look at what your Team thinks the constraints and the opportunities are.

Assess subscription renewals and team tools against your team's feedback about how they perform for them.

Prepare for your all-hands with the topics your team care about.

The 48 hours after an announcement is when you find out what actually landed, as opposed to what you think was communicated.

Gather context and opportunities to improve from the teams on the frontline supporting incidents.

Gather post-launch sentiment

The formal reason a deal was lost is written by whoever fills in the field. The real one is usually in a rep's head.

Your handover document is mostly a reconstruction of what you happen to remember. The Team Vault already holds the open items, so use it as the source and write the handover from that.

If you're taking over, the Team Memory is the fastest way to understand what's actually happening, rather than what the last set of slides said.

And if you're handing a Team over, the record goes with the Organisation, so context doesn't leave with you.

You've heard of a Spotify year in review - now you can prepare one for your team. A year of responses is a genuine history of your team work.

Use leep to prepare annual planning, using quotes and thematics to support your planning and hypotheses.