Blindsided
The deadline that slipped quietly.
Fine in every check-in, right up until it wasn’t.
For managers
Know where your team stands. Help it get more done.
Ambient Assist keeps a live read on your team’s work, answers your questions about anyone on it, flags what needs you while it’s small and offers to take everyone’s busywork. You report with confidence, and your team gets more done.
Reduced motion is on, so the orb is resting.
The problem
Chasing status. Still blindsided.
You’re in so many meetings you can’t see the work. Status means nudging people, problems surface after they’re expensive, and your best people lose hours to busywork.
Flat-footed
“Where are we on this?”
Your boss asks, and you need a day to find out.
Micromanaging
Checking in too often.
Because you can’t see the work, and your team feels it.
Busywork
Great people on small tasks.
Hours a week on follow-ups, look-ups and write-ups.
With Ambient Assist
Know your team’s pulse. Lift its output.
Knowing
A live read on your team.
Decisions, commitments and progress from your team’s meetings and tools, with a heads-up when something needs you. Ask about anyone on the team and get a straight answer.
- Heads-ups while problems are small
- Ask about anyone on your team, anytime
- Updates for leadership in minutes, with sources
- One-on-ones that start from what actually happened
- Know how each person works best
Doing
A team that gets more done.
Each person’s work scout offers to take their follow-ups, look-ups and write-ups. They say yes to what helps, and the team’s hours go to the work that matters.
- Nothing runs without the person’s yes
- It only offers what its tools can finish
- More done, without more hours
A manager’s morning
Already knowing the answer.
An example of a morning: what needs you, answers about your people, your update for leadership, and what your team got done.
ExampleDana’s desktop app
Thu, Oct 8 · 8:00 AM
Ambient Assist
YESTERDAY
Payments integration is about a week behind. The vendor’s sandbox slipped, and the team plans to recover by October 20. Platform sync · Oct 6, 2:22 PM Platform sync · Oct 6, 2:24 PM
TODAY · SESSION
completed: Leadership update — Your leadership update is drafted: Launch on track except payments, recovering by October 20. Both open roles filled. One risk to watch: the vendor sandbox.
DR
Greg’s been quiet this week. Is he keeping up with the billing migration?
Mostly. He’s closed three of the five migration tasks. The last two are waiting on API keys he asked IT for on Tuesday, and he’s spent most of the week on support escalations. [Linear, BIL-112] [IT request, Tue] [Support queue]
DR
Is Jill busy right now? I’d like to pull her into the payments call.
Yes. She’s been on the vendor call since 7:30.
DR
What did the team’s assistants take off their plates this week?
Maya’s launch timeline page, two meeting summaries and the launch-review prep.
accepted: Draft a first-week plan for the two new hires starting November 2
completed: Draft a first-week plan for the two new hires starting November 2 — The first-week plan is ready in your wiki: who each new hire pairs with, and the launch-week tasks they can take.
Thursday, October 8TODAY1 activity
7:50 AM
ACTIVITYRead the drafted leadership update.
Wednesday, October 7TODAY3 activities · 1 meeting
5:05 PM
ACTIVITYReviewed the sandbox workaround with Jill.
2:20 PM
ACTIVITYBoth offer letters signed; told the team.
11:15 AM
ACTIVITYMoved the payments dates in the migration plan.
9:30 AM
Hiring sync with HRMeeting · 9:30 AM – 10:00 AM
Tuesday, October 6TODAY1 activity · 2 meetings
2:00 PM
Platform syncMeeting · 2:00 PM – 2:40 PM
10:00 AM
Launch planningMeeting · 10:00 AM – 10:45 AM
9:05 AM
ACTIVITYWent over the migration plan before planning.
Monday, October 5TODAY1 activity · 1 meeting
4:00 PM
Final interviewsMeeting · 4:00 PM – 5:30 PM
1:15 PM
ACTIVITYRead the two candidates’ take-home work.
TODAY
No activity recorded on this day.
October
4 days with records.
Tuesday, October 6TODAY2 notes
Maya sends the revised timeline by Friday.
The payments vendor’s sandbox slipped a week. The team plans to recover by October 20.
Wednesday, October 7TODAY1 note
Both offers are accepted. The new hires start November 2.
TODAY
No notes captured on this day.
October
2 days with captures (of any kind).
Tuesday, October 6TODAY2 action items
Tell Marcus the platform roles are filled.
Get a firm sandbox date from the vendor.
TODAY
No action items captured on this day.
October
2 days with captures (of any kind).
Index
project
- - BIL-112: moving billing to the new plans. (project, updated Oct 6)
- - PAY-318: payments for the self-serve launch. (project, updated Oct 7)
- - Platform’s two open roles. (project, updated Oct 7)
type: projecttitle: Payments integrationdescription: PAY-318: payments for the self-serve launch.
Payments integration
Status
About a week behind: the vendor’s sandbox slipped. Recovery is planned for October 20. Platform sync · Oct 6, 2:22 PM
Facts
- Jill is working on a sandbox workaround with the vendor. Platform sync · Oct 6, 2:28 PM
- One of the launch’s three workstreams, with the billing migration and exports. Launch planning · Oct 6, 10:04 AM
Open questions
- What happens to the launch if the sandbox isn’t back by October 20?
type: projecttitle: Billing migrationdescription: BIL-112: moving billing to the new plans.
Billing migration
Status
Three of its five tasks are closed; the last two wait on API keys. Platform sync · Oct 6, 2:33 PM
Facts
- The keys were asked for from IT on Tuesday. Platform sync · Oct 6, 2:34 PM
- It ships with payments for the November 9 launch. Launch planning · Oct 6, 10:04 AM
type: projecttitle: Platform hiringdescription: Platform’s two open roles.
Platform hiring
Status
Both roles are filled. The new hires start November 2. Hiring sync with HR · Oct 7, 9:52 AM
Facts
- Until then, two engineers carry three launches. Launch planning · Oct 6, 10:38 AM
Platform teamdaily11h agoRunweekly3d agoRunmonthly7d agoRunyearlyneverRun
Progressupdated 11h ago
The projects and workstreams — where each stands, what moved, what is next.
- Payments (PAY-318) is about a week behind; the vendor’s sandbox slipped, and recovery is planned for October 20.
- The billing migration (BIL-112) has three of its five tasks closed; the last two wait on API keys.
- Both open roles are filled; the new hires start November 2.
Decisionsupdated 11h ago
What was decided, when and why; what was reversed or is still open.
- For this launch, payments keeps its vendor and works around the sandbox rather than switching.
Risksupdated 11h ago
Blockers, slipping dates and open dependencies — and what would resolve them.
- If the sandbox isn’t back by October 20, payments slips the launch.
- Two engineers carry three launches until November 2.
Practicesupdated 3d ago
How the work gets done — rituals, tools, hand-offs.
- Status at Tuesday’s sync, decisions at Thursday’s launch review.
- Dates go into a plan written down, each with its source.
Acquired knowledge
When each insight was learned, newest first.
WED, OCT 7
Both open roles are filled; the new hires start November 2.
TUE, OCT 6
Payments is a week behind: the vendor’s sandbox slipped.
Payments keeps its vendor and works around the sandbox.
SUN, OCT 4
Status at Tuesday’s sync, decisions at Thursday’s launch review.
Offerswork the agent proposes to take off your plate — nothing runs without your accept
Draft a first-week plan for the two new hires starting November 2
They start a week before the launch, while the team is at its busiest.
EVIDENCE
- Wednesday’s hiring sync
- Tuesday’s launch planning
No open offers.
Scheduled workaccepted offers and jobs you created in chat — ask “every morning at 8, summarize yesterday”
Leadership updatePauseRun nowDelete
Every Thursday at 7:45, draft my leadership update from the week’s meetings and tracker.
LAST RUN 15M AGO · COMPLETED · Your leadership update is drafted: Launch on track except payments, recovering by October 20. Both open roles filled. One risk to watch: the vendor sandbox.
Draft a first-week plan for the two new hires starting November 2Run nowDelete
Running
LAST RUN JUST NOW · COMPLETED · The first-week plan is ready in your wiki: who each new hire pairs with, and the launch-week tasks they can take.
The scoutScan now
Last scan: 35m ago
Recent results
The first-week plan is ready in your wiki: who each new hire pairs with, and the launch-week tasks they can take.
Your leadership update is drafted: Launch on track except payments, recovering by October 20. Both open roles filled. One risk to watch: the vendor sandbox.
Shared knowledge
What your team knows, in one place.
An example: your team’s projects, decisions and risks, kept current from its meetings and tools, with a heads-up while a problem is still small.
ExampleDana’s account page, on the web
Thu, Oct 8 · 8:00 AM
Ambient AssistAccount
DRdana.reyes@lumenfield.example
Lumenfield
Your assistant
Chat
Ask your assistant
Today
You ·
Greg’s been quiet this week. Is he keeping up with the billing migration?
Ambient Assist ·
Mostly. He’s closed three of the five migration tasks. The last two are waiting on API keys he asked IT for on Tuesday, and he’s spent most of the week on support escalations. [Linear, BIL-112] [IT request, Tue] [Support queue]
You ·
Is Jill busy right now? I’d like to pull her into the payments call.
Ambient Assist ·
Yes. She’s been on the vendor call since 7:30.
You ·
What did the team’s assistants take off their plates this week?
Ambient Assist ·
Maya’s launch timeline page, two meeting summaries and the launch-review prep.
Lumenfield · Your people
Your people
People
The people of your teams
| Person |
|---|
| GNgreg.novak@lumenfield.examplePlatform |
| JPjill.park@lumenfield.examplePlatform |
| MOmaya.okafor@lumenfield.examplePlatform |
Lumenfield · Shared knowledge
The Platform team
What the Platform team knows and how its work is going.
Platform wiki
Index
project
- Billing migration - BIL-112: moving billing to the new plans. (project, updated Oct 6)
- Payments integration - PAY-318: payments for the self-serve launch. (project, updated Oct 7)
- Platform hiring - Platform’s two open roles. (project, updated Oct 7)
projects
Payments integration
project · updated Yesterday
PAY-318: payments for the self-serve launch.
Status
About a week behind: the vendor’s sandbox slipped. Recovery is planned for October 20. Platform sync · Oct 6, 2:22 PM
Facts
- Jill is working on a sandbox workaround with the vendor. Platform sync · Oct 6, 2:28 PM
- One of the launch’s three workstreams, with the billing migration and exports. Launch planning · Oct 6, 10:04 AM
Open questions
- What happens to the launch if the sandbox isn’t back by October 20?
projects
Billing migration
project · updated 2 days ago
BIL-112: moving billing to the new plans.
Status
Three of its five tasks are closed; the last two wait on API keys. Platform sync · Oct 6, 2:33 PM
Facts
- The keys were asked for from IT on Tuesday. Platform sync · Oct 6, 2:34 PM
- It ships with payments for the November 9 launch. Launch planning · Oct 6, 10:04 AM
projects
Platform hiring
project · updated Yesterday
Platform’s two open roles.
Status
Both roles are filled. The new hires start November 2. Hiring sync with HR · Oct 7, 9:52 AM
Facts
- Until then, two engineers carry three launches. Launch planning · Oct 6, 10:38 AM
3 pages in this wiki.
Heads-ups
Standing
Payments integration is about a week behind. The vendor’s sandbox slipped, and the team plans to recover by October 20. Platform sync · Oct 6, 2:22 PM Platform sync · Oct 6, 2:24 PM
Heads-ups
Resolved
No load-test plan two weeks before launch week.
How the team’s work is going. About the work, never about people.
The Platform team’s intelligence
Progress
The projects and workstreams: where each stands, what moved, what is next.
Updated 11 hours ago
- Payments (PAY-318) is about a week behind; the vendor’s sandbox slipped, and recovery is planned for October 20.
- The billing migration (BIL-112) has three of its five tasks closed; the last two wait on API keys.
- Both open roles are filled; the new hires start November 2.
The Platform team’s intelligence
Decisions
What was decided, when and why; what was reversed or is still open.
Updated 11 hours ago
- For this launch, payments keeps its vendor and works around the sandbox rather than switching.
The Platform team’s intelligence
Risks
Blockers, slipping dates and open dependencies, and what would resolve them.
Updated 11 hours ago
- If the sandbox isn’t back by October 20, payments slips the launch.
- Two engineers carry three launches until November 2.
The Platform team’s intelligence
Practices
How the work gets done: rituals, tools, hand-offs.
Updated 3 days ago
- Status at Tuesday’s sync, decisions at Thursday’s launch review.
- Dates go into a plan written down, each with its source.
Acquired knowledge
What was learned, and when
- Progress · daily
Both open roles are filled; the new hires start November 2.
- Risks · daily
Payments is a week behind: the vendor’s sandbox slipped.
- Decisions · daily
Payments keeps its vendor and works around the sandbox.
- Practices · weekly
Status at Tuesday’s sync, decisions at Thursday’s launch review.
Why Ambient Assist
We know the “where are we on this?” feeling.
Needing a day to answer a simple question isn’t a people problem. It’s a visibility problem. Ambient Assist gives you a second set of eyes on the work, and gives your team a hand with the busywork.
Catches commitments
Decisions and action items from every meeting, with owners.
Checks claims
Against your team’s tools, while the topic is still open.
Speaks up early
Only when something needs you, never just to talk.
Shows its sources
Every note and update links to where it came from.
[Quote from a manager about knowing where the team stood, and the team getting more done.]
How it works
Three steps to a team you can see.
-
Bring your team on.
Everyone signs in with your organization, set up once from one admin dashboard.
-
It follows the work.
Meetings, commitments and progress, with a heads-up when something needs you and offers that take the busywork.
-
Ask, or get the summary.
Plain answers anytime, and an update ready for your next one-on-one or leadership meeting.
Our promises
- No rankings or scores of people, ever
- Nothing runs without the person’s yes
- Every claim has a source
- Your organization decides what’s on
- AI keys your organization controls
How it works, in detail: see the FAQ on the homepage, or book a call.
The short version
Lead from what you know.
You’re in the middle: answering to the people above you and responsible for the people below. Most days that means chasing status and hoping nothing’s slipping. Ambient Assist gives you a live read on your team’s work, from their meetings and their tools, and a heads-up while problems are still small. Ask about anyone on your team and get a straight answer. Your update for leadership is ready in minutes, with sources. And because everyone on your team has an assistant that offers to take their busywork, the team gets more done without working more hours. Bring Ambient Assist to your team, and lead with confidence.
Know your team. Lift its output.
Everyone signs in with your organization. You set it up once, from one dashboard.
Windows 10 and 11 · macOS 13 or later · Questions? Book a call