FT
FollowThrough
concept prototype
Shadow weekonboarding
Friday, August 14

Good morning, Maya

7 commitments are still open. This is your one digest for the day, and nothing here has been sent.

Interruptions today
1 digest, 0 pings
Nothing today was urgent enough to interrupt you.
7 of 7 still to goApprove level. Nothing sends without your OK.
Jump toYou owe 3Owed to you 2No owner 2
Show

You owe

3

Things you said you would do.

Overdue

You told Priya in Tuesday's QBR you'd send revised pricing by Thu.

Deadline passed yesterday. No pricing sent, no reply on the thread.

Evidence
  • Meeting transcript / Meridian Freight QBR, Tue Aug 11"I'll get you revised pricing by Thursday." 00:41:22
  • Email thread / Re: Meridian renewal terms, 6 messagesLast message Aug 11. No attachment sent since.
  • Doc / Meridian pricing v3 (draft)Last edited by you Aug 12. Never shared externally.
SuggestedSend a nudge Goes outside the companyVery sure 94%

Send Priya the revised pricing with a one line status.

You said it out loud, with a name and a date attached.

To priya.raghavan@meridianfreight.com
Subject Revised pricing for the renewal

Hi Priya, Following up on Tuesday. Revised pricing is attached, with the volume tier we discussed applied from month one. Two things changed from the version you saw: the tier break moves from 500 to 400 seats, and onboarding is folded into year one instead of billed separately. Happy to walk through it Thursday if that is easier than reading it cold. Maya

Written to sound like the mail you already send. Nothing goes out until you click below.

Overdue

You promised Elena the security review summary after Monday's call.

3 days late. Review doc exists but was never sent.

Evidence
  • Meeting transcript / Security review, Mon Aug 10"I'll write this up and send it over." 00:52:10
  • Doc / Security review notes, Aug 10Created by you Aug 10. Not shared with Elena.
SuggestedSend a recapFairly sure 83%

Send the recap you already wrote, trimmed to what she asked for.

Clear promise, but "after the call" is not a date.

Coming up

You told Rosa you'd send the Cobalt go/no-go summary before Monday's launch review.

Due Monday Aug 17, two working days out counting today. Nothing drafted yet.

Evidence
  • Meeting transcript / Cobalt launch checkpoint, Wed Aug 12"I'll have the go/no-go summary to you before Monday." 00:18:47
  • Doc / Cobalt launch checklist6 of 9 items closed. No summary doc exists yet.
  • Jira ticket / COB-214, Webhook retries drop eventsStill open. This is the one item the summary has to cover.
SuggestedWrite it early Goes outside the companyVery sure 91%

Write the summary now, while the standup notes are fresh, and hold it for your Monday send.

You named a day, and nothing is written yet.

Owed to you

2

Things other people said they would do for you.

Overdue

Marcus said he'd open the integration escalation for Bellwether by Friday.

End of week passed. No ticket exists in the Bellwether project.

Evidence
  • Meeting transcript / Bellwether sync, Thu Aug 6"I'll open the escalation before end of week." 00:12:04
  • Jira ticket / BWH project, escalation query0 tickets created since Aug 6. Expected 1.
SuggestedSend a nudgeFairly sure 88%

Nudge Marcus with the two lines he needs to file it.

Marcus named himself. The date is our read of "end of week".

What should this mute?

You can turn any of these back on in settings.

This one stops showing up, and nothing else changes.

Say why and the commitment is closed, so nothing chases it again. Leave it blank and the commitment stays open.

Quiet

Bellwether Health has not replied to your Aug 6 renewal thread.

9 days quiet. Renewal date Aug 28.

Evidence
  • Email thread / Renewal paperwork, Bellwether HealthYour message Aug 6. No reply since.
  • Doc / Account record, Bellwether HealthRenewal date Aug 28. Owner: you.
SuggestedSend a nudge Goes outside the companyLess sure 79%

Short check in that gives them an easy way to answer.

Nobody promised anything here, just a quiet thread with a renewal date.

No owner

2

Came up in a meeting and nobody picked it up.

Overdue

Cobalt Systems integration blocker was raised twice with no owner.

Raised Aug 5 and Aug 13. Ships Aug 21. Still unassigned.

Evidence
  • Meeting transcript / Integrations standup, Thu Aug 13"Cobalt is still blocked on the webhook retry." 00:07:33
  • Jira ticket / COB-214, Webhook retries drop eventsUnassigned. Priority not set. Opened Aug 5.
  • Email thread / Cobalt launch checklistShip date Aug 21 confirmed by Cobalt on Aug 11.
SuggestedFlag a blockerFairly sure 86%

Flag to Nadia with both mentions and the ship date.

Raised twice, and the ship date is a week out.

Quiet

Roadmap review produced an action item with no owner and no ticket.

7 days since the meeting. No ticket, no thread, no owner.

Evidence
  • Meeting transcript / Q4 roadmap review, Fri Aug 7"Someone needs to scope the audit log export before we commit." 00:28:51
  • Jira ticket / ARC backlog, keyword scanNo ticket mentions audit log export.
SuggestedOpen a ticketFairly sure 81%

Open a ticket in ARC and assign it to the review owner.

The task is clear. We guessed the owner from the rest of the meeting.

2 more scored under 60%, so FollowThrough left them out.Change the cutoff in settings.

Concept prototype. Fictional people, companies, and evidence. Not a Glean product and not affiliated with Glean.