Set Up a Shared Team Workflow

This is a starter skill for turning a useful individual workflow into a shared team process. Adapt it to the team's existing tools, responsibilities, privacy boundaries, and way of working rather than treating the outline as a fixed method.

Context, setup, and planning

Try to understand the result, team, source systems, shared destination, ownership, review points, privacy boundaries, and what a successful handoff means. Existing team documentation, workspace files, process notes, templates, and approved systems can help when they are relevant and available; they are not prerequisites. Offer to learn through a few questions, inspect that existing context, or combine both.

Before changing anything, show the team a concise plan covering inputs, owners, destination, review points, and the intended approach. Where useful, agree on one representative example, template, or reporting cadence to calibrate the workflow before expanding it.

Execution

1. Start with one accepted workflow rather than redesigning all of the team's operations.
2. Map the workflow from approved inputs to a reviewable output. Keep responsibilities and approval boundaries explicit.
3. Preserve source links or other provenance needed to review shared findings and updates.
4. Put reusable team guidance and shared artifacts in the team workspace. Keep different clients' data separate, and do not move personal, client-confidential, or unapproved context into shared files.
5. Run a small pilot with the people responsible for the work. Verify permissions, handoffs, field meanings, and review behavior before scaling.
6. Preserve the accepted process as a team-visible skill or shared guide. Add a Routine only when the team explicitly wants recurring execution.

Ask for approval before sending sensitive communications, changing access, or making irreversible updates.

Suggested outcome

Create a concise, reusable team workflow with clear inputs, owners, shared destinations, field meanings, review points, privacy boundaries, and a verified first handoff. Teammates should be able to repeat the process without guessing what another person meant.

Suggested next steps

• Use strawberry/recruiting/onboard-offboard-teammates when the workflow must be added to a teammate's onboarding or removed during offboarding.
• Add a Routine only after the team accepts the manual or assisted first run.
• Invite additional teammates only when the user wants them involved in the shared workflow.