About this session
Two Studios, One Build: Collaborate Across Boundaries is a 90-minute to half-day in-person team building workshop for teams who want to practice cross-team collaboration. Separate studios each build one part of a shared product, then find out whether it all fits together.
Cross-team work depends on the handoffs: shared assumptions, timely changes and messages that arrive. This hands-on build makes those moments visible without the stakes of a real project.
Participants leave with clearer ways to define interfaces, share changes early and test together, plus a few practices to try with a real partner team.
What your people take away
- Build separate modules of one shared product
- Agree interfaces before building the connecting parts
- Communicate changes to other teams early and clearly
- Test whether the parts work together
- Trace failures to builds, agreements or missed messages
Shared with you
See the full session
Create your free Workbliss profile to see the rest of this outline and book it. It takes a minute, with your work email.
- What each length covers, 90 minutes to half day
- Everything that’s covered, part by part
- Book online, and browse 1,500+ more sessions for your teams
Already a member? Sign in
What each length covers
90 minutes
Build apart, connect togetherStudios build separate parts of one product and agree how their modules will connect. Participants see how clear interfaces and early updates prevent rework.
- Build separate modules of one shared product
- Agree interfaces and communicate changes
Covers 2 of 4 parts: Build separate modules of one shared product and Agree interfaces and communicate changes.
Half day
Build, integrate and apply the lessonsAdds a full integration test, a review of what failed and why, and a second attempt. Teams finish by agreeing practices to try with a real partner team.
- Build separate modules of one shared product
- Agree interfaces and communicate changes
- Test whether the parts work together
- Take the lessons into real cross-team work
Covers all 4 parts.
What’s covered
Build separate modules of one shared product
Every length- Get your studio's briefEach studio receives its part of a shared build, such as a bridge or a marble run, with its own materials and constraints.
- Build without seeing the other studioTeams work in separate spaces, so everything they know about the other module comes through messages.
- Join the modules for a first checkThe studios bring their parts together and see where sizes, connections or assumptions don't match.
Agree interfaces and communicate changes
Every length- Define the connection pointsStudios agree exactly where and how their modules meet, including sizes, heights and what passes between them.
- Set a rhythm for updatesTeams choose how and when to message each other, so changes reach the other studio before they cause problems.
- Handle a change mid-buildThe facilitator introduces a change request, and teams practice deciding who needs to know and how fast.
Test whether the parts work together
Half day only- Run a full integration testStudios connect their final modules and test the whole build against the original brief.
- Trace failures back to their causeTeams check whether problems came from the build, the interface agreement or a message that never arrived.
- Fix and test againStudios make one round of agreed fixes and run the test a second time.
Take the lessons into real cross-team work
Half day only- Map your real handoffsParticipants identify the teams they depend on and the connection points that most often cause friction.
- Agree practices to tryTeams choose practical changes, like shared definitions or regular check-ins, to test with one partner team.
Tools and materials
- Building materials and tools, provided
- Studio brief cards
- Interface agreement template
- Change request cards
- Integration test checklist
- Partner team action plan
Who it’s for
- Teams that depend on each other to deliver
- Product, engineering and operations groups
- Departments working across sites or functions
- Project and program leads managing handoffs
How booking works
- Book online. Create a free Workbliss profile, then pay with session credits, by card or by invoice.
- Pick a date. Choose a date at least 14 days ahead, or book now and set the date later.
- Choose your expert. Within 3 working days, we send you profiles of the experts available for your date.
- We deliver it. Your expert is briefed on your people and goals, then runs the session live online or at your site.
Questions about Two Studios, One Build: Collaborate Across Boundaries
How long is Two Studios, One Build: Collaborate Across Boundaries?
Two Studios, One Build: Collaborate Across Boundaries runs as 90 minutes or half day. You choose the length when you book. A 90-minute session covers Build separate modules of one shared product and Agree interfaces and communicate changes. A half-day session adds Test whether the parts work together and Take the lessons into real cross-team work.
Can Two Studios, One Build: Collaborate Across Boundaries be delivered online or in person?
It is delivered in person, at your site, in any country.
How do we book Two Studios, One Build: Collaborate Across Boundaries?
Create a free Workbliss profile with your work email, then open Two Studios, One Build: Collaborate Across Boundaries to see the price for each length and book it. You can pay with session credits, by card or by invoice, and choose a date at least 14 days ahead, or set it later.
Who leads the session?
A vetted Workbliss expert, briefed on your people, culture and goals before the session. After you book, we send you profiles of the experts available for your date within 3 working days, so you can choose who leads it.
Can it be tailored to our company?
Yes. Every session is shaped around your goals, your people and the benefits you already offer, and delivered by experts in your people’s languages.