Guide

The Product and Engineering Manager playbook

See your tickets, reviews and the whole team’s progress in one place, so you spend less time asking for updates.

Start with what you need today.

Product and engineering manager
1 · Your day , jump to this chapter 2 · Team progress , jump to this chapter 3 · Decisions : decisions and context, jump to this chapter 4 · People : your team and stakeholders, jump to this chapter 5 · What shipped , jump to this chapter
Chapter 01~1 min read

Start here

This guide is for people who lead product or engineering teams.

Tickets are in Linear. Reviews are in GitHub. Decisions are in Slack and docs. You open each one to see where things are. The 11 plays below bring them together in Humble, around five questions:

  • Your day: What needs me today?
  • Team progress: Where are we, without asking?
  • Decisions: Why did we decide this?
  • People: What did we say last time?
  • What shipped: What did we deliver?

Start with the question that matters most to you. Each play is one idea, not a rule. Fewer tabs help everyone, and most of all people with attention deficit hyperactivity disorder (ADHD).

Chapter 02~2 min read · two plays

Your day

What needs me today?

Play 1: See tickets, reviews and meetings in one list

The situation

You check Linear, GitHub and your calendar in separate tabs, and reviews wait while you are in meetings.

In Humble

  1. Connect Linear and GitHub in Humble. Tickets due soon and review requests appear in My Tasks.
  2. Connect your calendar, so meetings sit next to your tasks.
  3. Keep reviews in Now, and clear any that are more than a day old.

What changes: you start the day from one list, and nobody waits days for a review.

My Tasks in Humble, with a GitHub review request, your own task and Linear tickets in one list.

Play 2: Sort the day into Now, Next and Later

The situation

Everything feels urgent at once.

In Humble

  1. Drag anything that blocks a teammate, or is due today, into Now.
  2. Put this week in Next, and the rest in Later.

What changes: you know what to do first, and the rest waits without being lost.

My Tasks as a board in Humble. A task that blocks a teammate moves into Now.
Chapter 03~2 min read · two plays

Team progress

Where are we, without asking?

Play 3: Read the team timeline before the stand-up

The situation

The stand-up is people reading out what is already in Linear and GitHub.

In Humble

  1. Create a shared space for the team. Closed tickets and merged pull requests appear on the team timeline.
  2. Engineers keep working in Linear and GitHub. They never need to open Humble.
  3. Read the timeline first, and use the stand-up for blockers only.

What changes: stand-ups are shorter, and nobody writes the update by hand.

The shared team timeline in Humble. Work from Linear, GitHub and the calendar appears without anyone writing an update.

Play 4: Find what is stuck, and offer help

The situation

Work stays “nearly done” for a week, and nobody says it is stuck.

In Humble

  1. Filter the team timeline by project and week.
  2. If a project went quiet, ask a kind, open question, such as “Can I help?”

What changes: you find stuck work in days, not weeks. The timeline shows progress. It is not a way to watch people.

The team timeline in Humble, filtered to one project. A quiet week is a reason to offer help.
Chapter 04~2 min read · three plays

Decisions and context

Why did we decide this?

Play 5: Give each feature one home

The situation

The spec, design and tickets are in three places, and new people have to ask for each one.

In Humble

  1. Write a note for the feature, such as Spec: CSV export.
  2. Link the spec, the design page and the Linear tickets, and add the project tag.
  3. Point new teammates to these notes first.

What changes: anyone can find the context without asking you.

A feature note in Humble, with the spec, the design and the Linear tickets linked to it. New teammates can start here.

Play 6: Write each decision down

The situation

Months later, nobody remembers why the team chose one way over another.

In Humble

  1. After a decision, write a short note with the template below.
  2. Tag it #Decision and link the tasks it affects.

What changes: the team does not make the same decision twice.

A decision note to copy

  • Decision: what we chose, in one sentence.
  • Why: the main reason.
  • Not chosen: the other options, and why not.
  • Who and when: names and the date.
  • Next steps: linked tasks, each with an owner.

Play 7: Keep the AI chats behind the work

The situation

A Claude or ChatGPT chat had good ideas, and now you cannot find it.

In Humble

  1. Use the browser extension to save the chat to the task it belongs to.

What changes: good thinking stays with the work, and others can build on it.

A task in Humble with the spec and two AI chats under Related items.
“…being able to answer… questions from customers without having to hand them off to other teams… we’ve reduced time to first resolution times for certain case types by 50–60%…”
Alex Rose
Chief Product & Technology Officer, Social Value Portal
Chapter 05~2 min read · two plays

Your team and stakeholders

What did we say last time?

Play 8: Run one-to-ones that build on the last one

The situation

Each one-to-one starts from nothing, and promises get lost.

In Humble

  1. Keep one note per person, such as 1:1: Nilu.
  2. Turn what you agree into tasks, linked to the note.

What changes: each one-to-one picks up where the last one ended.

A one-to-one note in Humble, with the tasks you agreed linked to it.

Play 9: Keep customer context in one place

The situation

A customer told sales about a problem, and you have to ask them again.

In Humble

  1. Save key customers as contacts, for example from LinkedIn with the browser extension.
  2. Open the person before a call to see their notes, emails, meetings and tasks. Teammates can share their notes with you.

What changes: customers do not repeat themselves, and feedback reaches the people who build.

A customer's timeline in Humble: notes, emails, meetings and tasks with that person in one place.
Chapter 06~2 min read · two plays

What shipped

What did we deliver?

Play 10: Write the weekly update in minutes

The situation

The Friday update takes an hour of digging through tools.

In Humble

  1. Open the team timeline, pick this week and filter by project.
  2. Write three short parts with the template below, and add why it matters.

What changes: the update is quick, and it is based on what happened.

An update to copy

  • Shipped: the two or three things that matter most, and why.
  • Next: what the team works on next week.
  • Help needed: one blocker, and who can help.

Play 11: Look back over a cycle or a review period

The situation

You remember the last few weeks well, and the rest less well.

In Humble

  1. Filter the timeline by person or by week. Closed tickets and merged pull requests are there.
  2. During the cycle, send Humble a Slack message or voice note when something goes wrong. It appears on your timeline.
  3. Write a review note, and turn each lesson into a task.

What changes: reviews are fairer, and each cycle teaches the team something.

My timeline in Humble, set to one week in May. Closed tickets and merged pull requests are already there.
Chapter 07~3 min read

The working rhythm

Small habits, at four speeds. Change them to fit your team’s cycles.

Every day: start from one list

  • Sort My Tasks into Now, Next and Later.
  • Clear any review that is more than a day old.
  • Read the team timeline before the stand-up.

Every week: look back, then ahead

  • Filter the team timeline by this week, and write the update.
  • Look for projects that went quiet, and ask if you can help.

Every cycle: plan and review

  • Check that each feature has its spec, design and tickets linked.
  • Run the cycle review from the timeline and your notes.
  • Turn each thing to try into a task with an owner.

Every quarter: step back

  • Read the decision notes from the quarter. Do any need a second look?
  • Look at the time you spent with each customer and team.
  • Collect examples for performance reviews while they are fresh.
Chapter 08~4 min read

How to organise this in Humble

There is no single correct setup. The structure below is a simple place to start.

What goes where

When you have… A useful place for it
A ticket or review requestMy Tasks, from Linear and GitHub
A closed ticket or merged pull requestThe team timeline, added for you
A featureA spec note, with the doc, design and tickets linked
A decisionDecision note, tagged #Decision
A useful AI chatSaved to its task
A team memberA one-to-one note, and tasks you agree
A customer or stakeholderContact, with notes and a timeline
A quick thought or problemA Slack message or voice note to Humble

Shared spaces

One shared space per team or product area is usually enough, such as Platform team. Share it only with the people who work in it.

Tags

Project
#Export#Search#Onboarding
Type
#Decision#Spec#Review#1-1

Keep tags few and plain. Linear already holds your ticket labels. Tags in Humble are for the notes, decisions and people around the tickets.

Naming

  • Spec notes: Spec: [feature].
  • Decision notes: Decision: [what], [month].
  • One-to-one notes: 1:1: [name].
  • Reviews: Review: Cycle [number].
  • Tasks: start with a verb, such as “Write the hiring brief”.
Chapter 09~2 min read · 30 min to do

The 30-minute setup

A first version in half an hour. It does not need to hold everything to be useful.

0–5 minutesConnect Linear and GitHub in Humble.You’ll have: Tickets and reviews in My Tasks, and shipped work on the timeline.
5–10 minutesConnect Google or Outlook Calendar and install the browser extension.You’ll have: Your meetings next to your tasks, in every new tab.
10–15 minutesCreate a shared space for your team and invite the team.You’ll have: One shared team timeline.
15–20 minutesSort My Tasks into Now, Next and Later. Add the tasks that are not tickets.You’ll have: A clear first step for tomorrow.
20–25 minutesWrite a one-to-one note for each person on your team, and one spec note for your main feature.You’ll have: Places to keep what you agree and why.
25–30 minutesAdd Humble to Slack. Put a weekly half hour in your calendar to write the update from the timeline.You’ll have: A way to save thoughts, and a habit to keep it going.

You bring the judgement, the priorities and the care for your team. Humble brings the work from Linear and GitHub together, so you spend less time asking and more time helping.

See how it works in Humble

The plays in this guide use features available in Humble today.

See how Humble brings your tickets, reviews, notes and the team’s progress together. You can also read about Humble for Linear and Humble for GitHub.

See how Humble works See Humble for your team
Chapter 11~1 min read

About this guide

This guide was written by the Humble team, based on how product and engineering managers can use the product in their day-to-day work.

It is a practical guide to one way of working, not the only way to lead a team. Every team is different, so use the parts that help and change the rest.

The quote in chapter 4 is from a call with Alex Rose about his team’s work with Humble. The examples in chapters 3 and 6 are made up to show how the plays fit together. They are not customer quotes. The names, tickets and dates in the product pictures are made up too. The guide describes Humble as of October 2026. Some product details may change over time.

Last reviewed: 1 October 2026.

Found something wrong or missing? Email hello@thehumbleai.com. We read everything.

Keep reading

Read this next

The chief of staff playbook
Running yourself, your exec and the leadership team from one place, without becoming the single point of failure for "what's happening".
Read the guide →

Browse: All guides

Want to try it yourself first?

No team rollout and no commitment. Connect Linear and GitHub, use Humble for one cycle, and see whether having your tickets, reviews and the team’s progress in one place makes the work easier to lead.

Get Humble