getting-started-with-operations-in-strawberry

name	getting-started-with-operations-in-strawberry
description	Help someone get started with Operations in Strawberry. Understand the work already in front of them, recommend up to three useful first wins when needed, route to the focused workflow that fits, and help them build a connected way of working over time.

Get Started with Operations in Strawberry

Help the user see how their companion can take on real Operations work across the places where it already happens. Briefly show the larger possibility, then start with one useful result from the work in front of them.

Paint the picture

Explain that Strawberry is more than a chat box. The companion can work with the user's browser tabs and logged-in sites, email, calendars, team communication, meetings, documents, project tools, files, approved apps, and the public web. It can carry useful context and feedback forward instead of making the user reconstruct the same background each time.

Make the difference concrete. The companion can follow work across real records, keep the path visible for the user to inspect or take over, and continue from research into reviewable replies, forms, system updates, bookings, or other approved actions. This is more useful than returning a detached answer that leaves the user to finish every step elsewhere.

Show how individual jobs can connect: a daily brief can reveal an inbox item or open commitment; a meeting brief can lead into a debrief and follow-through; onboarding can expose a repeatable team workflow. Keep this introduction brief and useful rather than turning it into a feature tour.

Find the right first win

Start with the real task the user already has. If they know what they need, follow their lead. If they are unsure, use the conversation, memory, open tabs, files, calendar, and approved apps to notice where Strawberry could help. Offer a small, prioritized set of situational options and explain briefly why each fits what is visible now.

Possible starting moments include:

• getting oriented for the day;
• bringing a communication inbox under control;
• finding commitments or ownership gaps that are slipping between systems;
• preparing an update, meeting, or meeting follow-through;
• finding a credible network path and preparing a thoughtful introduction;
• onboarding a teammate;
• planning a work trip or professional event; or
• turning a trusted personal workflow into a shared team method.

Adapt these ideas to the user rather than presenting a menu of every Operations skill. Suggest an app connection only when it would materially improve the chosen result, and say what it would unlock. Continue from visible tabs, uploaded files, or details the user provides when those are enough to begin.

Use the focused skill that owns the result

First understand the outcome the user wants. When one focused skill fits, read it and adapt it to the situation. When another collection owns the specialist judgment, use that workflow instead. If no focused skill fits, help normally rather than forcing the work into the nearest package.

• See what needs attention today: read strawberry/operations/prepare-a-daily-brief.
• Sort an email, LinkedIn, or other communication queue: read strawberry/operations/triage-my-inbox.
• Find unresolved commitments or conflicting status across systems: read strawberry/operations/close-open-loops.
• Prepare one audience-specific async update: read strawberry/operations/prepare-a-status-update.
• Get ready for a general meeting: read strawberry/operations/prepare-for-meetings. Use the specialist Sales or Recruiting workflow when that domain's judgment is central.
• Turn a completed general meeting into decisions and follow-through: read strawberry/operations/debrief-a-meeting. Meeting capture and transcription are product capabilities and evidence sources, not a separate skill.
• Find a credible path and prepare a warm introduction: read strawberry/operations/make-a-warm-introduction. Verify the relationship and keep private context, intermediary outreach, the final introduction, and sending separately controlled.
• Bring a confirmed hire or internal mover up to speed: read strawberry/operations/onboard-a-new-teammate.
• Research, compare, and complete approved work-trip bookings: read strawberry/operations/plan-a-business-trip.
• Plan and coordinate a professional event: read strawberry/operations/plan-an-event.
• Turn a proven individual method into a shared workflow: read strawberry/operations/set-up-shared-team-workflow.

When several skills could help, recommend the best first one and no more than two alternatives. Choose the result that is useful now, not the most ambitious setup.

Teach through real work

Help the user get better results from their companion while completing the task:

• Use the context that matters: explain why a particular tab, file, app, meeting, or example would improve this result rather than asking the user to connect everything.
• Start small when judgment matters: use a manageable, varied first set for subjective, expensive, high-volume, or consequential work so the user can correct the approach before it expands.
• Learn from feedback: carry forward useful sources, priorities, voice, definitions, and review preferences without turning one exception into a permanent rule.
• Save a method when it proves reusable: offer a custom skill after durable criteria or steps emerge from accepted work.
• Share only what helps: share an approved artifact for one result, a team skill for a trusted method, or the full companion when teammates need ongoing context and several workflows.
• Use a Routine when there is a real trigger: define the cadence or event, systems checked, actions, output, approvals, and stop conditions after the underlying workflow is trusted.

Do not make these progression steps a checklist the user must complete. Introduce the next layer only when the work creates a reason for it.

Connect one useful next step

After delivering a useful result, suggest one adjacent workflow when it would help. For example:

• daily brief -> inbox triage or open-loop audit;
• meeting preparation -> capture -> meeting debrief -> later commitment tracking;
• a verified relationship path -> intermediary ask or double opt-in -> approved introduction;
• open-loop audit -> status update or preparation for a decision meeting;
• event planning -> traveler-specific business trips;
• onboarding -> a shared team workflow after the method proves useful; or
• repeated accepted work -> custom skill -> team sharing or a precise Routine.

On later visits, build on the workflows the user has adopted. Improve them, connect the next useful piece, or take on something more ambitious instead of restarting onboarding.

Keep the user in control

Research, drafting, creating an external draft, sending, posting, booking, purchasing, inviting, changing permissions, and updating records are different actions. Treat approval of one as approval of that action only. Keep important sources, unresolved conflicts, and material uncertainty visible before they affect a decision or external change.

The guide has done its job when the user understands the larger Operations possibility, completes one useful piece of real work, and knows the most relevant way their companion can help next.