How Our Team Works
Jack explains how the team communicates, divides responsibilities, and handles deadlines. Grace also discusses when to ask for help and how decisions are made.
Dialogue11

Now that you’ve had a chance to settle in, Jack can walk you through how we work day to day. Jump in with questions whenever something isn’t clear.
We use chat for quick questions and updates, but anything that needs a decision or a clear record goes in the project tracker. That way, nobody has to dig through old messages.
That makes sense. If I’m working on a task and realize I’m waiting on someone else, should I message them directly, or update the tracker first?
Do both if it affects the timeline: send them a quick note, then flag the dependency in the tracker. If there’s no deadline risk, a tracker update is usually enough.
And don’t feel you need to solve every snag on your own. Try a reasonable next step, but if you’re blocked or the impact could spread, raise it early.
When you say “raise it early,” do you mean tell you, Jack, or whoever owns that part of the project? I want to make sure I’m not creating extra noise.
Start with the person closest to the issue, and loop me in if it changes priorities, involves a trade-off, or you can’t get a clear answer. A short heads-up is rarely noise.
As for responsibilities, each task has one owner, even when several people contribute. The owner keeps it moving, checks the handoffs, and speaks up if the scope starts to creep.
Got it. And if two deadlines clash, should I decide which one to prioritize based on impact, or check with you before I move anything around?
Use impact to bring a recommendation, but don’t quietly reshuffle agreed deadlines. Tell me what’s competing and why; we’ll weigh the risks and agree on a plan.
Exactly. We try to make decisions with the people doing the work, not behind closed doors. Emma, does that give you a clear picture, or is there a part we should unpack further?
Vocabulary7
- walk you through
To explain something step by step. Use it when offering to show someone how a process works.
- project tracker
A shared tool for recording tasks, decisions, and progress. In this dialogue, it keeps important information easy to find.
- flag the dependency
To clearly mark that a task depends on someone or something else. This helps the team notice possible delays.
- blocked
Unable to make progress because something is in the way. You can say you’re blocked when you need help or information to continue.
- loop me in
To include someone in a conversation or keep them informed. Use it when another person should know about an issue or decision.
- scope starts to creep
The amount of work gradually grows beyond what was originally agreed. This phrase is useful for raising concerns about extra tasks or changing requirements.
- reshuffle agreed deadlines
To change the order or timing of deadlines that the team has already accepted. The phrase suggests discussing changes rather than making them silently.
Key Sentences7
- 1
We use chat for quick questions and updates, but anything that needs a decision or a clear record goes in the project tracker.
This sentence clearly explains which communication channel to use for different kinds of information. Reuse the structure to describe how your team handles messages, records, or requests.
- 2
Do both if it affects the timeline: send them a quick note, then flag the dependency in the tracker.
This gives practical, ordered instructions for handling work that may be delayed. Reuse “Do both if…” to explain when two actions are needed.
- 3
Try a reasonable next step, but if you’re blocked or the impact could spread, raise it early.
This balances taking initiative with asking for help before a problem grows. You can reuse it to encourage someone to act independently while escalating serious issues.
- 4
Start with the person closest to the issue, and loop me in if it changes priorities, involves a trade-off, or you can’t get a clear answer.
This explains who to contact first and when to involve someone else. Reuse the pattern to set clear escalation steps for a problem.
- 5
The owner keeps it moving, checks the handoffs, and speaks up if the scope starts to creep.
This summarizes the responsibilities of the person accountable for a task. You can adapt it to describe what a task owner should do on your team.
- 6
Use impact to bring a recommendation, but don’t quietly reshuffle agreed deadlines.
This encourages thoughtful recommendations while making clear that deadline changes need discussion. Reuse it when someone must prioritize competing work without changing commitments on their own.
- 7
We try to make decisions with the people doing the work, not behind closed doors.
This expresses an inclusive approach to decision-making. Use the contrast “with…, not…” to explain how your team wants decisions to be made.