Making Claude Part of How the Team Works
Workshops, use-case roadmaps, and embedded engineering for a biotech that had Claude but wasn't using it
Challenge
A mid-size biotech had bought Claude licenses and run a pilot, but the value stayed inside two or three early adopters. Most of the team had tried Claude once, didn't find it useful for their actual work, and stopped opening it. Leadership saw the bill and didn't see the outcomes.
Solution
We ran AI Foundations workshops for both leadership and working teams using the company's own documents. Then we built a use-case roadmap rooted in how the team actually worked. From there, we ran the AI Assist Program with three business leaders, pairing each with a Trackmind engineer to build Claude into their real calendars, decisions, and processes.
Outcome
Claude moved from a tool people had heard of to part of how the team plans, drafts, reviews, and decides. The leaders we paired with adopted workflows they kept using, and their teams started copying them without anyone having to push.
The Story
The Starting Point: A Pilot That Stalled
The team had access. They had training videos. They had a Teams channel where someone occasionally posted a prompt that worked. For most people, the gap between knowing Claude existed and using it for actual work was wider than any documentation could close. The work they did wasn't generic. It was their company's literature reviews, their regulatory drafts, their internal memos. Generic training never crossed that gap.
The Approach: Start with the Work, Not the Tool
We didn't run a Claude features tour. The working sessions in our AI Foundations workshops used the team's own documents. Then we sat with three business leaders and traced a real week of their work. Where they got stuck, where they repeated themselves, where they'd asked a junior person to do something they could have done with Claude in ten minutes if they'd known how. Each leader walked out with two or three workflows built specifically around them. Their teams saw the workflows, asked how they were made, and the spread started without us having to drive it.
The Impact
Claude became something the team uses without thinking about it. The leaders we worked with stopped putting off tasks until they had time, because the workflow was built and the friction was gone. New people joining the team get pointed at the workflows on day one.
What We Built
Training & enablement
- • AI Foundations workshops for leadership and working teams
- • Use-case discovery grounded in the team's own documents
- • Internal Claude playbook tailored to the company
- • Onboarding materials for new hires
Embedded engineering
- • AI Assist Program (1:1 leader and engineer pairings)
- • Custom Skills for the team's repeated workflows
- • MCP connectors to internal systems
- • Ongoing tuning based on how the workflows are actually used
The Takeaway
When you build Claude into the processes a team already runs, you stop having to convince anyone to adopt it. They use it because using it is now how the work is done.
Ready to make Claude part of how your team works?
Let's build the workflows where your team will actually use them.
Start Your Project