Operations work starts with a simple question. What needs attention today? Answering it means checking the calendar, Slack, email, project tools, meeting notes, and a few tabs. Then the next step is an update, an introduction, or access for a new teammate.
Strawberry can do that checking in the same browser where the work continues, show where sources disagree, prepare the next action, and remember the definitions you accept. A brief or a meeting feeds the next task instead of becoming another isolated result.
What Strawberry can help you do
Not sure where to begin? Your companion can look at the Operations work you have open and suggest a useful skill to try first.
/getting-started-with-operations-in-strawberry Get a clearer view of the day
A useful daily brief saves you from doing the same round of checking every morning. Strawberry can review the calendar, messages, tasks, meeting notes, and current project context, then pull out the few priorities, conflicts, decisions, and risks that may change your plan. The supporting links stay close by when you want to check the detail.
Inbox triage can work in a similar way. Your inbox might be email, LinkedIn, or another messaging service. Strawberry reads the relevant thread and any useful surrounding context, then brings forward the messages that need a decision or reply. It can draft responses in the same channel and prepare a group of cleanup actions for you to review.
Some follow-ups are harder to spot because the evidence is spread around. A meeting note may name an owner, while the project tracker has no assignment and a later Slack message suggests the work is already finished. Close Open Loops checks those sources together and shows you the mismatch, the evidence behind it, and the smallest useful next step.
See what needs attention today
Review the calendar, messages, tasks, meeting notes, and current work, then bring forward what could change the day.
/prepare-a-daily-brief Bring an inbox under control
Read the useful surrounding context across email, LinkedIn, or another queue, find what needs a decision, and prepare replies or cleanup for review.
/triage-my-inbox Find the open loops
Reconcile commitments, follow-ups, ownership gaps, and conflicting status across the systems where work happened.
/close-open-loops Write updates people can use
Status updates take time because the latest picture is rarely sitting in one tidy document. Your companion can bring together the project record, recent decisions, dashboards, meeting notes, and team messages, then compare them with the last update before drafting the new one.
The draft is shaped for the people reading it. A leadership update may need the consequence of a delay and a clear decision. A delivery team may need the changed priority, owner, and dependency. When two sources disagree, Strawberry keeps that visible instead of quietly choosing the version that makes the update look complete.
/prepare-a-status-update Prepare for meetings and finish the follow-up
For an upcoming meeting, Strawberry can start with the calendar event, match the right attendees, and follow the useful links into earlier messages, project records, documents, and relevant web pages. The brief stays focused on the outcome you need, what has changed, and the questions worth asking.
Once the meeting is over, your companion can work from a transcript captured without a visible meeting bot, your notes, or another reliable record. It separates accepted decisions and commitments from ideas that were only discussed, prepares the follow-up, and proposes updates to the appropriate tools. You still review a message or record change before it is applied.
When the next step is an introduction, Strawberry can inspect approved relationship context, verify whether a warm path is credible, and prepare an intermediary ask or double opt-in without exposing private context.
Walk into the meeting prepared
Bring together the people, history, changed context, desired outcome, and questions worth asking.
/prepare-for-meetings Turn the conversation into follow-through
Separate discussion from decisions and prepare the actions, messages, and record updates that follow.
/debrief-a-meeting Make a considerate introduction
Check whether the relationship path is credible and prepare the right intermediary ask or double opt-in.
/make-a-warm-introduction Plan trips and events
Once you find a promising travel or event option, you still need to check current availability, compare the full cost and terms, sign in to the right account, fill in a form, and make sure the choice works with the calendar and the people involved.
When research arrives as a separate list of links, you usually have to reopen the pages, recover the current price or availability, and repeat the context before you can act. That handoff is especially awkward when the useful information sits behind a login or the choice changes while you are making it.
In Strawberry, that work happens in the same browser you can see. Your companion can start from the dates, policy, budget, and preferences already available, open the relevant flight, rail, accommodation, venue, catering, and vendor sites, and keep the useful options ready for you to inspect. After you choose, it can continue through an inquiry or booking flow. Contacting a provider, accepting terms, and spending money remain separate approvals.
Plan a business trip
Use the dates, policy, budget, calendar, and preferences to compare a coherent itinerary, continue into approved bookings, and organize the confirmations.
/plan-a-business-trip Plan a work event
Connect the concept, attendees, venues, vendors, budget, invitations, logistics, and run-of-show.
/plan-an-event Help a new teammate find their feet
New teammates usually receive plenty of information. The harder part is working out what to read first, who to meet, which projects matter to their role, and whether they have the access needed to contribute.
Strawberry can assemble a role-aware path from Notion, Slack, Drive, calendars, project tools, files, and the relevant admin pages. It flags stale or conflicting material, prepares introductions and access requests, and can complete approved setup when the onboarding owner has authority. The internal coordination view stays separate from what the new teammate should see.
/onboard-a-new-teammate Keep the methods that work
After you have corrected a few real results, you will start to see which parts should stay consistent: the sources to check, the order of work, the team's definitions, the format, and the points that need a person to review them. Those details can become a custom skill so the next run begins with the method you have already worked out.
- Share an approved artifact when someone only needs the result.
- Share a team skill when colleagues need the same sources, definitions, method, and review points.
- Use a shared companion when several workflows need the same ongoing context.
- Create a Routine when the trigger, systems, destination, ownership, and stop conditions are clear.
/set-up-shared-team-workflow