Back to Blog & Insights

Business Growth

Start a Business Collaboration Small

A furniture maker and textile designer can use one upholstered stool to test roles, pace and quality before discussing recurring work.

By WWA Editorial Team 4 min read
Two women fit a fabric panel to an unfinished stool during a small workshop collaboration.

A promising collaborator can look ideal on paper and still create friction once work begins. A furniture maker may admire a textile designer’s material sense, yet neither knows whether briefs will be clear, decisions timely or handoffs compatible with production. Committing immediately to recurring work asks those questions too late. A one-time pilot gives both people a bounded way to observe the work before investing more calendar time, attention or business identity in the relationship.

Build one piece of real work

Consider a furniture maker and textile designer developing one upholstered stool. The maker can build the frame, establish dimensions and prepare the upholstery surface. The designer can develop the fabric approach, specify placement and finishing, and address how texture, color and wear affect the piece. One small object contains meaningful work for both without becoming a new product line.

Before work begins, agree what the stool should demonstrate and who might use it. The point is to test the collaboration on a concrete customer-facing piece, with constraints both people can see. Define the deliverable as one finished prototype, with agreed photographs and a short record of decisions, then set a build window and brief review period.

INSEAD Knowledge’s approach to testing a new way of working recommends a small task that resembles real work, a clear measure, a bounded exercise and a debrief of trade-offs. That structure keeps a pilot finite and produces evidence about how the collaborators work together.

Success measures should describe the work itself. The pair can assess whether the finished stool meets its agreed quality standard, materials arrive when needed, changes are resolved without confusion and each person can complete her part without repeated intervention. Those signals are more useful than a general feeling that the collaboration went well.

Make ownership visible early

Separate responsibilities before the first cut of wood or fabric. One person should coordinate the brief, schedule, decisions and checkpoint. IESE Insight’s collaboration guidance highlights the value of a named project owner for implementation-heavy work, while outside collaborators contribute specialized ideas or perspective. The owner gives the pilot an operating center without taking over the other person’s creative role.

In this example, the furniture maker might coordinate the production sequence because the prototype moves through her workshop. The textile designer owns the fabric recommendation and upholstery direction. They can agree which decisions require both voices, such as a material substitution, and which sit with the relevant specialist. At a midpoint checkpoint, they can ask whether the frame is ready for fabric, whether the textile works with the structure and whether either workload has expanded beyond the original scope.

This is a focused working experiment, distinct from a referral arrangement or a formal joint venture. Its purpose is to learn whether complementary skills and working rhythms fit on one defined piece of work. Keeping the purpose narrow makes it easier to discuss time, visibility, sensitive information and differing expectations—concerns IESE identifies as reasons to start small.

Debrief the coordination, not only the object

When the stool is complete, review the result while details are fresh. Discuss construction, finish and whether the textile treatment served the intended design. Then examine coordination: Were instructions usable? Did feedback arrive at the right moment? Did the checkpoint surface problems early enough? Was the division of responsibility practical under real constraints?

IESE’s corporate-venturing research distinguishes a joint proof of concept—a one-time collaboration to develop or improve a product or service—from a partnership built around recurring joint proofs of concept. The same distinction helps independent professionals avoid treating a promising first project as a long-term commitment. The finished stool is evidence from their own context, rather than a prediction based on portfolios or rapport. End the debrief with a direct choice: continue with another defined project, change the scope or working terms, or stop.

Sources