Know what matters before you ask.

ThinkBox continuously understands what’s happening across your work and brings you what needs your attention.

Your work is talking.
Here’s what matters.

ThinkBox connects the signals across your tools, understands the context, and brings the important developments into focus.

01 · Noise
Requests, updates, and reminders arrive across your working day.
02 · Relevance
A blocked auth fix, an open Jira issue, and QA’s expected build need a closer look. Routine updates stay in the background.

Noise
Relevance
Connection
Your Pack

Slack#design

Jordan Lee08:00

Can you review this before standup?

DocsPeople

Two workshop sessions were added.

OutlookLearning

Learning team

Upcoming session

The next session is on Wednesday.

Slack#community

Casey Chen11:21

The volunteer calendar has been shared.

OutlookOffice

Office team

Holiday calendar

The holiday calendar is ready.

Slack#team

Alex Morgan

Team lunch photos are in the channel.

DocsPlanning14:42

Last quarter’s notes are archived.

OutlookProjects

Project team

Show-and-tell topics

Please suggest a show-and-tell topic.

DocsPeople

Mentoring sign-ups close next week.

OutlookLearning

Learning team08:03

Next team talk

Any topics for the next team talk?

Slack#community

Casey Chen

This week’s event roundup is ready.

OutlookOffice

Office team

Next week’s all-hands

Please RSVP to next week’s all-hands.

WikiOperations11:24

Planning notes are ready to review.

DocsPlanning

The retro template has been updated.

OutlookProjects

Project team

Monthly review notes

The monthly review notes are ready.

DocsPeople14:45

The starter checklist has been updated.

OutlookLearning

Learning team

Workshop reminder

Reminder: the workshop starts at two.

WikiKnowledge

The team FAQ has new answers.

OutlookOffice

Office team08:06

Meeting room confirmed

Your meeting room is confirmed.

WikiOperations

Who is handling equipment requests?

DocsPlanning

Can you add to the draft agenda?

OutlookProjects

Project team11:27

Editorial review

Can you join the editorial review?

JiraWebsite

The testing checklist is ready.

OutlookLearning

Learning team

Course reading list

Your course reading list is ready.

WikiKnowledge14:48

The shared library is up to date.

OutlookOffice

Office team

Visitor details

Visitor instructions have been updated.

WikiOperations

The supplier directory has been refreshed.

JiraInternal

Following up on yesterday’s thread.

OutlookProjects

Project team

Customer debrief

The customer debrief moved to Thursday.

JiraWebsite

Please check the revised estimate.

OutlookLearning

Learning team11:30

Workshop recording

Your workshop recording is ready to watch.

WikiKnowledge

The handbook index has been reorganized.

Slack#design

Jordan Lee

The design review moved to tomorrow.

Slack#platform

Alex Morgan02:14

Auth fix is blocked. We can’t hand over the build.

Blocker reported overnight.

Jira

Token refresh fix still unresolved.

Required for your release.

OutlookQA

QA team09:00

Release build expected

QA expects the release build this morning.

The next team is waiting.

03 · Connection

The release may be at risk.

An unresolved authentication issue is blocking the build QA expects this morning.

04 · Your delivery Pack Needs your attention

Release handoff may be at risk

The auth fix remains unresolved, and QA is expecting the build this morning.

Why this matters to you

Your team owns the release. A delayed handoff leaves QA waiting and puts the release schedule at risk.

Suggested next step

Confirm an owner and revised handoff time.

View sources · Slack, Jira AUTH-241, QA email

SLACK / PLATFORM
Auth fix is blocked. We can’t hand over the build.
JIRA / AUTH-241
Token refresh fix still unresolved.
OUTLOOK / QA
QA expects the release build this morning.

Three signals. A shared dependency. A clearer next step.

FROM SIGNAL TO NEXT STEP

A familiar chat.
Already up to speed.

Your signal, sources, and context are already here. Ask a follow-up and work out what comes next.

Release handoff

3 sources attached

Sources 3

Slack / PlatformAuth fix blocked

Auth fix is blocked. We can’t hand over the build.

Jira / AUTH-241Token refresh unresolved

Token refresh fix still unresolved.

Status: Open

Email / QARelease build expected

QA expects the release build this morning.

ThinkBox

The release handoff may be at risk. Platform reports a blocked auth fix, AUTH-241 is still open, and QA expects the build this morning.

You

What should I confirm next?

ThinkBox

Confirm who owns AUTH-241 and when the fix will be ready. Then align a revised handoff time with QA.

Jira / AUTH-241 Email / QA

Insights

Owner and ETA need confirmation.

Suggested next step

Confirm an owner and revised handoff time with Platform and QA.

An owner, fix ETA, and revised handoff time still need confirmation.

Illustrative conversation

YOUR DAY, A STEP AHEAD

Know before
you walk into the room.

The release. The renewal. The promise someone made.
See what needs you before the next conversation.

Before standup

“Why am I only hearing about this now?”

The release plan looks fine. The review queue and the incident channel tell a different story.

Research behind this pattern

Hostaway described reviews concentrating among a small group of developers, causing work to accumulate.

Read Swarmia / Hostaway ↗

These companies are not presented as ThinkBox customers. The people and records in this demo are fictional.

What ThinkBox brings you

ThinkBox Pack

11:00 · Release cutoff at 14:00

The release cuts at 2. Its last review is still waiting.

GitHub / PR #431 / Waiting 26 hours
Auth retry fix: checks passed. Maya is the only requested reviewer.
Slack / #incidents / 10:42
Maya: Still on the payments incident. I can’t review until after lunch.
Release plan / Atlas 2.8
The auth fix must merge before today’s 14:00 branch cut.

Why this needs you

The release depends on a review whose assigned owner is occupied.

Your next move

Confirm another qualified reviewer before the branch cut.

Prepare the review handoff

Before the planning review

“We planned the work. Where did the week go?”

Your migration starts today. The engineers assigned to it are still carrying last week’s escalations.

Research behind this pattern

Jellyfish described unplanned work carrying into weeks intended for roadmap focus, even after introducing support rotations.

Read Jellyfish ↗

These companies are not presented as ThinkBox customers. The people and records in this demo are fictional.

What ThinkBox brings you

ThinkBox Pack

09:15 · Planning review at 10:30

Your migration team is still on last week’s incident.

Rotation plan
Rahul and Nina finish support duty Friday. Migration work starts Monday.
Escalation board / 09:05
Three customer escalations remain assigned to Rahul and Nina.
Project Atlas / Wednesday milestone
Both engineers own the first migration rehearsal. No handoff is recorded.

Why this needs you

The plan assumes a clean handoff. The open work does not show one.

Your next move

Agree who takes the escalations before confirming the rehearsal date.

Prepare the planning decision

Before the renewal call

“I thought this account was healthy.”

The CRM is green. The person doing the work is still asking for a fix.

Research behind this pattern

ComplianceQuest described a strategic customer that kept paying and providing references while support emails revealed frustration.

Read ChurnZero / ComplianceQuest ↗

These companies are not presented as ThinkBox customers. The people and records in this demo are fictional.

What ThinkBox brings you

ThinkBox Pack

08:30 · Renewal call tomorrow

Tomorrow’s renewal call has a problem your CRM missed.

CRM / Brookside Health
Health: Green. Renewal call tomorrow. Last invoice paid.
Support / Export issue #218
Reopened three times in 12 days. Latest status: waiting for engineering.
Customer email / Yesterday
We’re still reconciling the exports manually. Can someone give us a real update?

Why this needs you

The account status and the customer’s experience are out of sync.

Your next move

Confirm the fix status and bring a recovery plan to tomorrow’s call.

Prepare the customer conversation

Before prioritization

“That small request is somebody’s whole workflow.”

The integration was parked as too complex. The same missing step is now surfacing in customer rollouts.

Research behind this pattern

Intercom nearly shelved a Salesforce integration because of complexity, then revisited it with a smaller implementation after Sales highlighted demand.

Read Intercom ↗

These companies are not presented as ThinkBox customers. The people and records in this demo are fictional.

What ThinkBox brings you

ThinkBox Pack

10:00 · Prioritization at 14:00

The integration you parked is holding up two rollouts.

Roadmap / Case sync
Deferred: full conversation-to-case mapping is too complex for this cycle.
CS notes / Aster + Cedar
Both rollout plans list automatic case creation as an open dependency.
Customer call / Yesterday
One-way case creation is enough. We don’t need full two-way sync.

Why this needs you

The smallest useful version may be narrower than the version you deferred.

Your next move

Validate a one-way pilot with both customers before reprioritizing the full integration.

Shape the smallest useful release

Before the forecast call

“The deal says Friday. Does the buyer?”

The close date is still in this week’s forecast. A condition from the buyer’s last email hasn’t made it into the plan.

Research behind this pattern

SpotOn describes using customer interaction evidence to investigate deal risk and correct forecasts. The security-review scenario is our own demonstration.

Read Gong / SpotOn ↗

These companies are not presented as ThinkBox customers. The people and records in this demo are fictional.

What ThinkBox brings you

ThinkBox Pack

09:00 · Forecast call at 11:00

Your Friday close is waiting on Security.

CRM / Northline / $120K ARR
Stage: Commit. Expected signature: Friday.
Buyer email / Monday
We can sign once Security approves the questionnaire.
Internal handoff / #deal-desk
Questionnaire attached. Security owner: unassigned. No completion date recorded.

Why this needs you

The signature depends on an approval that has no confirmed owner or timing.

Your next move

Get an owner and completion date, then verify Friday with the buyer.

Prepare the deal unblock

Before the next escalation

“The answer exists. Why is the customer still waiting?”

The customer is chasing the update you promised. Engineering has already posted a workaround in another tool.

Research behind this pattern

Column described missed SLAs and lost emails across fragmented workflows. The workaround and ticket records here are our own demonstration.

Read Front / Column ↗

These companies are not presented as ThinkBox customers. The people and records in this demo are fictional.

What ThinkBox brings you

ThinkBox Pack

11:10 · Customer update due at noon

You promised an update by noon. Engineering already replied.

Support / Ticket #7621
Waiting on engineering for 18 hours. Jordan promised an update by 12:00.
Jira / ENG-218 / 09:12
Workaround verified in staging: disable scheduled export and retry manually.
Ticket activity / 11:00
No engineering update linked. Customer: Any news before our reporting run?

Why this needs you

An internal answer is available, but the customer handoff has not happened.

Your next move

Confirm the workaround is safe for this customer and send the promised update.

Prepare the customer update

A library we’re building

Give every team its best hand.

We’re building a library of hundreds of Packs for different teams and priorities.

Illustrative Pack previews

ThinkBox for enterprise

Your organization is one of a kind.
Your Packs can be, too.

For enterprise teams with specialized needs, we work with you to design bespoke Packs around your workflows, business context, and what matters across your organization.

For enterprise

Bespoke Packs

Designed with the ThinkBox team around your organization’s needs.

Designed with your team

Your workflows: The handoffs, decisions, and recurring work your teams manage.
Your business context: The accounts, projects, and relationships that give signals meaning.
Your priorities: What deserves attention, who needs to know, and why it matters.

Atlas 2.8 · 11:00 · Branch cut at 14:00

The code is ready. The release isn’t.

Two gates are verified. Review coverage and the canary plan still need confirmation.

Build and automated tests
CI #882 passed at 10:38.
Verified
Rollback rehearsal
The previous build was restored in staging, recorded in runbook v12.
Verified
Required review for PR #431
Maya is handling an incident. No replacement reviewer has accepted.
Missing
Canary observation plan
A traffic slice exists. The observation window, stop criteria, and observer are unconfirmed.
Incomplete

Decision needed by 13:00

Retain the window only after the remaining checks are confirmed. Otherwise, propose a revised cutoff.

Prepare gate review

Leo’s release-gate checklist

For release lead Leo to review before 13:00:

Confirm an available, qualified reviewer for PR #431 and their acceptance.
Name a canary observer and agree the observation window.
Agree comparison metrics against the current build.
Define stop criteria and who can halt the rollout.
Confirm the rollback owner and the runbook to use.

Preparation only. No review is assigned and no release is approved.

Example sources 3

Fictional records supporting this example, not live workspace data.

GitHub review state: PR #431 requires review; CI #882 passed at 10:38. No replacement reviewer has accepted.
Incident thread: Maya is handling an incident and cannot cover the required review.
Release runbook v12: Records the staging rollback rehearsal, 14:00 cutoff, and incomplete canary observation plan.

Pattern behind this Pack

Successful CI is not equivalent to complete release readiness. Canary evaluation and rollback preparation answer different questions.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

Google SRE · Canarying releases (opens in a new tab)

Northstar · Tuesday 09:00 · Renewal meeting Wednesday 10:00

Tomorrow’s renewal brief misses a reopened issue.

The account brief and the latest support and stakeholder evidence no longer agree.

What the brief says

Proposal delivered.
Account marked healthy six days ago.

What changed

Export ticket #1842 reopened today at 08:40.
The executive sponsor changed teams. A replacement is unconfirmed.

Interpretation, not a forecast

This is a briefing gap, not proof of churn. Current renewal intent is unknown.

Prepare renewal questions

Nia’s conversation preparation

CSM Nia should obtain the current Support state and update the brief before the meeting.

What is the reopened issue’s current business impact?
Who owns the renewal decision after the sponsor’s move?
What needs resolution or agreement before Wednesday’s meeting?

No renewal intent or replacement sponsor is assumed.

Example sources 3

Fictional records supporting this example, not live workspace data.

Account brief: Proposal delivered; health marked healthy six days ago.
Support ticket #1842: Export issue reopened Tuesday at 08:40.
Stakeholder notes: The executive sponsor changed teams; the replacement is not confirmed.

Pattern behind this Pack

Health assessments should be checked against current customer evidence and changes that need triage.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

Cedar · Day 21 of onboarding

People are signing in. The core workflow isn’t sticking.

Weekly activity is ahead of meaningful workflow completion. The agreed day-30 goal is 80 review completers.

Licensed users: 120
Weekly active: 84
Review completers: 28
Day-30 target: 80

Completion by team
Team	Active / seats	Review completers
Engineering	40 / 50	14
Operations	28 / 40	10
Support	16 / 30	4

Example data, not industry benchmarks. Support’s lead reports missing review permissions; affected users still need verification.

Recovery milestones

Today
Verify access
Confirm affected users and their review permissions.
Day 23
Run the workflow together
CSM Omar and the customer admin work through the review with team leads.
Day 28
Remeasure the outcome
Check completion and discuss whether the day-30 goal needs revision.

Draft recovery plan

Draft · Cedar workflow recovery

Our goal is a completed weekly review, not more logins alone. First, verify who cannot access the review and agree the access correction with the customer admin.

On day 23, Omar and the admin will run the workflow with team leads. On day 28, remeasure completion against the agreed 80-person target and discuss any goal revision.

Proposed plan for customer agreement; the example makes no access changes.

Example sources 3

Fictional records supporting this example, not live workspace data.

Day-21 usage snapshot: 120 seats, 84 weekly active users, and 28 core-review completers, with the team totals shown above.
Onboarding success plan: Agreed day-30 goal: 80 review completers.
Support lead’s report: Review permissions are reported missing; the affected-user list is not verified.

Pattern behind this Pack

Customer success plans connect adoption work to agreed customer outcomes, rather than activity counts alone.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

GitLab · Customer success management (opens in a new tab)

Meridian · Wednesday 10:00

Friday’s signature depends on a review nobody owns.

The milestones are recorded. The dependencies and buyer commitments still need alignment.

Close-plan dependencies

Complete
Commercial terms and legal redlines
Both are complete in the shared plan.
Wed · 17:00
Security review
Buyer-side owner and turnaround are unconfirmed.
Thu · 12:00
Procurement approval
Dana can proceed only after security clearance.
Fri · 16:00
Signature · tentative
Signer availability remains unverified.

Target ≠ commitment

The CRM close date is a target, not a confirmed customer commitment.

Draft buyer alignment note

Draft · Confirming the shared close plan

Could you confirm who will own the security review and when they expect to finish? Dana’s procurement approval depends on that clearance.

Please also confirm the signer’s availability for Friday. Once these dependencies are agreed, let’s update the shared plan together rather than treating the CRM target as a commitment.

Prepared locally. No buyer message is sent.

Example sources 3

Fictional records supporting this example, not live workspace data.

Shared close plan: Commercial terms and legal redlines complete; remaining milestones are Wednesday security, Thursday procurement, and tentative Friday signature.
Buyer alignment notes: No confirmed security owner, turnaround, or signer availability.
CRM opportunity: Friday is the recorded target close date.

Pattern behind this Pack

Closing a deal requires coordinating approvals and dependencies with the buyer, not just recording a date.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

GitLab · Deal closure (opens in a new tab)

Aperture · Before forecast review

The champion says yes. Budget approval is still unknown.

Technical agreement and buying authority are different kinds of evidence.

Stakeholders, evidence, and gaps
Person / role	Recorded evidence	What to confirm
Mina · Champion	Validated workflow fit.	Can she arrange the budget-owner conversation?
Luis · Possible budget owner	Mentioned in notes only.	Authority and funding are unverified.
Ravi · Security	Completed controls review.	Technical approval does not approve spending.
Eva · Procurement	Shared onboarding steps.	Awaiting an approved business case.

Evidence gap

No recorded agreement on investment authority or a measurable business outcome. Luis is not a confirmed economic buyer.

Prepare the next discovery call

Buying-decision discussion plan

Who approves this investment, and how can we confirm their authority?
What measurable business outcome and decision criteria matter?
Who must approve the business case and funding?
What steps follow the completed technical review?

Use Mina’s help to arrange the conversation; do not infer Luis’s authority from a name in notes.

Example sources 3

Fictional records supporting this example, not live workspace data.

Discovery notes: Mina validated workflow fit; Luis is mentioned as a possible budget owner.
Controls-review record: Ravi completed the security review, without investment approval.
Procurement notes: Eva shared onboarding steps and awaits the approved business case.

Pattern behind this Pack

Qualification distinguishes a champion, investment authority, decision criteria, and the decision process.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

GitLab · MEDDPPICC (opens in a new tab)

Northstar · Ticket #1842 · 11:40 · Update promised at noon

The update is due at noon. The workaround is in another thread.

A tested idea is available, but it has not been verified in this customer’s environment.

Confirmed facts

Large exports fail for this customer.
Engineering tested smaller batches in a sandbox at 11:15.
Elena owns the promised 12:00 update.

Still unknown

Whether the workaround succeeds in the customer environment.
Permanent-fix delivery time.
Whether other accounts are affected.

Review customer-update draft

Draft · Northstar update

We are continuing to investigate the export failures. Engineering tested smaller batches in a sandbox at 11:15; we have not yet verified that approach in your environment.

We do not have a confirmed delivery time for a permanent fix. We propose a further update at 12:30, even if the investigation is still in progress.

Elena must confirm the proposed 12:30 commitment before sending. Nothing is sent by this example.

Example sources 3

Fictional records supporting this example, not live workspace data.

Northstar ticket #1842: Large exports fail; Elena owns the promised noon update.
Engineering workaround thread: Smaller batches tested in a sandbox at 11:15; customer-environment validation is absent.
Investigation snapshot · 11:40: No confirmed fix ETA or evidence establishing impact on other accounts.

Pattern behind this Pack

Customer communication should separate verified facts from uncertainty and make the next update commitment clear.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

Atlassian · Incident communication (opens in a new tab)

Export service · 09:00

Nine tickets may describe the same failure.

Reports share a 403 error after the 08:00 version-2.8 rollout. A common cause is not confirmed.

Tickets since 08:10: 9
Distinct accounts: 6
Shared error: 403

Symptom clusters
Cluster	Reports	Evidence to compare
Admin exports	4	Permission claims
Scheduled exports	3	Worker versions
API exports	2	Request IDs

Accounts overlap across clusters. Six is the deduplicated account total.

Correlation, not causation

The timing does not prove that the deployment caused the failures. Assess representative evidence before declaring a shared incident.

Prepare incident assessment

Proposed assessment plan

Propose Priya as coordinator and confirm her acceptance.
Collect representative tickets, permission claims, worker versions, and request IDs.
Assess customer impact and severity against the service’s incident criteria.
Link cases if a shared incident is confirmed, while preserving each customer follow-up.

No coordinator is assigned and no incident is declared by this example.

Example sources 3

Fictional records supporting this example, not live workspace data.

Support queue · 08:10–09:00: Nine reports across six deduplicated accounts, with overlapping admin, scheduled, and API symptoms.
Rollout log: Version 2.8 was rolled out at 08:00.
Error excerpts: The reports share a 403 error; deployment causation remains unverified.

Pattern behind this Pack

Incident assessment brings evidence, coordination, and impact evaluation together before conclusions are treated as confirmed.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

Atlassian · Incident response (opens in a new tab)

Atlas exports · Monday 09:00 · Thursday announcement

The feature is ready. The launch tells a different story.

Engineering has verified one scope. Customer-facing materials still describe another.

Workstream readiness
Workstream / owner	Current evidence	Alignment needed
Engineering / Maya	10,000-row export limit verified.	Use this as the confirmed scope.
Docs / Riley	Draft promises 50,000 rows.	Correct the claim.
Sales enablement / Omar	Demo uses the old scope.	Update the demo.
Support / Elena	Runbook awaits limits and guidance.	Finish support guidance against confirmed scope.

Tuesday’s review

Check every workstream against one confirmed scope before retaining the Thursday announcement.

Prepare launch alignment

Atlas launch alignment checklist

Confirm the verified 10,000-row scope with Maya.
Ask Riley to revise the Docs claim and Omar to update the demo.
Complete Elena’s runbook with confirmed limits and customer guidance.
At Tuesday’s review, check all workstreams against that same scope.

This preparation does not approve the launch or change the announcement date.

Example sources 3

Fictional records supporting this example, not live workspace data.

Engineering verification: Maya’s evidence confirms the 10,000-row limit.
Docs and enablement drafts: Riley’s draft promises 50,000 rows; Omar’s demo uses old scope.
Support launch checklist: Elena’s runbook awaits confirmed limits and guidance.

Pattern behind this Pack

Launch coordination aligns the product scope with documentation, enablement, and support readiness.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

GitLab · New product introduction (opens in a new tab)

Orion connector · Monday 13:00

One dependency moved. Three plans haven’t caught up.

Platform confirmed that the API contract moved from Monday to Thursday. Downstream dates below are proposals, not accepted commitments.

Published versus proposed handoffs
Handoff / owner	Published date	Proposed date / dependency
Integration QA / Erik	This Friday	Next Tuesday · Erik must confirm.
Enablement demo / Omar	This Friday	Next Wednesday · Depends on QA.
Customer pilot / Nia	Next Monday	Next Thursday · Requires customer agreement.

Confirmed upstream · estimated downstream

Only Platform’s move to Thursday is confirmed. None of these downstream estimates has been accepted.

Draft dependency handoff

Draft · Orion schedule alignment

Platform has moved the API contract to Thursday. Erik, please validate the proposed next-Tuesday QA handoff. Omar, check the next-Wednesday demo against QA’s accepted plan.

Nia, seek customer agreement for a proposed next-Thursday pilot. Once owners accept feasible dates, update the shared plan and communicate the changes.

No dates are changed and no owner acceptance is implied.

Example sources 3

Fictional records supporting this example, not live workspace data.

Platform dependency update: API contract moved from Monday to Thursday; confirmed upstream change.
Published handoff plan: QA and enablement were this Friday; the pilot was next Monday.
Draft dependency assessment: Next Tuesday, Wednesday, and Thursday are unaccepted downstream estimates.

Pattern behind this Pack

Dependency mapping makes upstream changes and downstream owner commitments visible together.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

Atlassian · Dependency mapping (opens in a new tab)

Atlas launch · Decision due Tuesday 14:00

Two teams are waiting for one scope decision.

The launch path needs an explicit decision with conditions, evidence, and a communication owner.

Decision roles

Approver: Dana · VP Product
Driver: Riley · Product
Contributors: Engineering, Sales, Support
Inform after decision: Docs and Customer Success

Options and trade-offs
Option	Value	Conditions / uncertainty
Launch verified 10,000-row scope Thursday	Earlier customer value.	Correct claims and confirm pilot suitability.
Wait for 50,000 rows	Retains the proposed capability.	Engineering estimates two more weeks; validation remains uncertain.

Recommendation · not approval

Stage the launch only if pilot needs are met and claims are corrected. Dana has not approved this proposed direction.

Prepare decision record

Draft decision record

Decision: pending Dana’s approval; proposed direction is a conditional staged launch.
Owner and deadline: Dana, VP Product; Tuesday 14:00. Riley drives preparation.
Rationale: earlier value at verified scope, subject to pilot suitability.
Conditions: confirm pilot needs and correct customer-facing claims.
Outstanding evidence: pilot fit, corrected materials, and validation confidence for the larger scope.
Communication: inform Engineering, Sales, Support, Docs, and Customer Success of the accepted decision.

This is a draft record, not an approval or announcement.

Example sources 3

Fictional records supporting this example, not live workspace data.

Decision request: Dana is approver, Riley is driver; decision requested Tuesday at 14:00.
Scope verification and estimate: 10,000 rows verified; 50,000 rows estimated at two more weeks with uncertain validation.
Launch alignment notes: Pilot suitability and corrected claims are conditions still to confirm.

Pattern behind this Pack

Explicit decision roles and trade-offs help teams record who decides, why, and under which conditions.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

Platform · Next two weeks

Three commitments. The same two engineers.

The current estimates exceed the available capacity after on-call and leave. Priorities and accepted changes need a discussion.

Engineer-days available: 12
Estimated work: 16
Engineer-day gap: 4

Competing commitments
Commitment	Estimate	Context
Reliability recovery	6 days	The service has exhausted its error budget. This fictional internal policy prioritizes recovery.
Renewal integration	4 days	Customer checkpoint next Friday.
New export scope	6 days	Announcement date is still proposed.

Proposed allocation

Protect six recovery days and four integration days, leaving two for exports. Defer or reassign the other four export days after checking skills and dependencies.

Scenario-specific policy

Recovery priority comes from this fictional organization’s internal policy. It is not a universal rule, and the effort figures are estimates.

Prepare allocation discussion

Capacity discussion plan

Ask VP Engineering to confirm priorities with Product and Customer Success.
Verify the estimates and the 12 available engineer-days after on-call and leave.
Check skills and dependencies before deferring or reassigning four export days.
Agree feasible commitments without assuming overtime.
Communicate accepted changes to owners and the customer-facing teams.

No work is reassigned and no commitment is changed by the example.

Example sources 3

Fictional records supporting this example, not live workspace data.

Platform capacity plan: Two engineers have 12 engineer-days available over the next two weeks after on-call and leave.
Commitment estimates: Recovery: six days. Integration: four days. Export scope: six days. Total: 16 days.
Fictional reliability policy: This service’s exhausted error budget triggers an internal recovery priority; it is specific to this scenario.

Pattern behind this Pack

Capacity planning makes competing estimates explicit. Error-budget policies describe organization-specific responses to reliability limits.

These public sources describe operating practices. The people, organizations, and workspace records above are fictional.

A few things to know

Context before
you get started.

What is a Pack?

A Pack is a focused workspace around a situation that matters to your role. It brings together evidence, context, why it matters, and useful next steps or ways to investigate. Proactive discovery is the starting point; search helps you go further.

Is ThinkBox only for engineering teams?

No. ThinkBox serves medium-sized companies and enterprises. This page uses an engineering-manager scenario to show how related developments can matter to someone with responsibility for a release.

Is the opening a live workspace?

No. It is an illustrative scenario, using fictional Slack, Jira, and Outlook updates. It explains the product direction; it is not live customer data or a claim that an action has been taken. Available sources depend on your organization’s connections and permissions.

How do I access ThinkBox?

Open ThinkBox to continue through the product’s existing access flow. The current deployment uses a demo access gate.

Your attention. The right context.

See what deserves
a closer look.

Start with what matters to your work.

Open ThinkBox

Know what matters before you ask.

Your work is talking. Here’s what matters.

01 · Noise

02 · Relevance

Release build expected

The release may be at risk.

Release handoff may be at risk

Why this matters to you

Suggested next step

A familiar chat. Already up to speed.

Sources 3

Insights

Owner and ETA need confirmation.

Suggested next step

Know before you walk into the room.

“Why am I only hearing about this now?”

The release cuts at 2. Its last review is still waiting.

GitHub / PR #431 / Waiting 26 hours

Slack / #incidents / 10:42

Release plan / Atlas 2.8

Why this needs you

Your next move

“We planned the work. Where did the week go?”

Your migration team is still on last week’s incident.

Rotation plan

Escalation board / 09:05

Project Atlas / Wednesday milestone

Why this needs you

Your next move

“I thought this account was healthy.”

Tomorrow’s renewal call has a problem your CRM missed.

CRM / Brookside Health

Support / Export issue #218

Customer email / Yesterday

Why this needs you

Your next move

“That small request is somebody’s whole workflow.”

The integration you parked is holding up two rollouts.

Roadmap / Case sync

CS notes / Aster + Cedar

Customer call / Yesterday

Why this needs you

Your next move

“The deal says Friday. Does the buyer?”

Your Friday close is waiting on Security.

CRM / Northline / $120K ARR

Buyer email / Monday

Internal handoff / #deal-desk

Why this needs you

Your next move

“The answer exists. Why is the customer still waiting?”

You promised an update by noon. Engineering already replied.

Support / Ticket #7621

Jira / ENG-218 / 09:12

Ticket activity / 11:00

Why this needs you

Your next move

Give every team its best hand.

Your organization is one of a kind. Your Packs can be, too.

Bespoke Packs

Context before you get started.

See what deserves a closer look.

Your work is talking.
Here’s what matters.

A familiar chat.
Already up to speed.

Know before
you walk into the room.

Your organization is one of a kind.
Your Packs can be, too.

Context before
you get started.

See what deserves
a closer look.