11th November 2024
 · 
7 min read
Tagged: business · consulting

Managed vs Collaborative

How does a managed project differ from a collaborative project? And which one is the right one?

Photo by cottonbro studio

Anyone who reads this blog with any kind of regularity will know that I'm always in a perpetual state of self-evaluation. Constantly assessing how I fit within the design industry, and making sure I'm not "doing it wrong".

It's not at all a bad way to be; it is after all the foundation for continual improvement. Do something, evaluate the outcome, make changes for better outcomes next time. This constant state of being over the last three years has no doubt made me a better designer now than I was when I started. Stronger skills in more diverse areas, as well as much more knowledge and experience in the specific field in which I work.

however, It is not without its cost. As with continual improvement in a manufacturing setting takes time and money, so too does it take its fair share of my mental capacity to continually be improving my skills and business strategy. I have no doubt in my mind that I've spent more time thinking about both than anyone else currently working in it. Overthinking is how I roll.

With that said, I've been thinking about the different engagement styles I've seen and/or been involved with in design consulting. Not necessarily the business model by which a client may ingage with a designer, but how the project is handled between both parties. Really it boils down to two main styles. For lack of better names, I'll call them managed, and collaborative.

To be very clear; neither one is better, and each has an element of the other in it.

A managed engagement style is the more traditional of the two. Where a consultancy is engaged by the client to perform a certain scope of work. The consultant then takes that scope and manages the whole project through to delivery. In design consulting this would considered end-to-end.

Conversely, a collaborative engagement style is one where the consultant and client work very closely together for specific tasks throughout the duration of the project, often playing to each other strengths. The work scopes are often more bite-sized, open to evolving with the project.

Managed Engagement

A managed engagement style is what I "grew up" with. In it's most basic embodiment the client comes to a consultancy with a problem, and the consultant goes away to solve it. With some touch points for review along the way, the consultancy manages the project right through to completion. While completion may mean all the way to production, completion at the very least means that all the design work is finished.

In my observations, managed engagement is the default for medium and large businesses, engaging with medium or large consultancies. Possibly due to businesses being more willing to hand off work that is outside of their main business activities so they can focus on what they're good at. The consultancies taking on these kinds of projects also have more capacity and capability to handle the whole project in-house. There may be some chicken-and-egg effect too though, in that large end-to-end scopes of works generally require significant investment. Investment that is usually in the domain of a business with existing revenue streams to fund it (though not always).

Collaborative Engagement

Collaborative engagement on the other hand I often see in the domain of small businesses and startups, working closely with small and medium consultancies. The work scopes are often taken in smaller chunks, usually only big enough to reach the next stage or answer the next big question. Meaning, there is still much more design work to be done. Yet while smaller pieces each, they usually add up to the same completed design objective. Collaborative engagement is also often performed with multiple consultancies simultaneously, coming from multiple disciplines. This creates a similar team environment - often of high-performing individuals, without the inherent overheads of having them all under the one roof.

I think the collaborative approach works well with startups in particular for two reasons. First, there are many unknowns in startup land. Both technical (and clinical) unknowns, and also financial unknowns. For startups working with small and medium consultancies on progressive chunks of work, the commitment is easier to budget for and the risks easier to track. There is often little desire to commit to the full development towards production if a startup doesn't yet know if the proof of concept will work. Secondly, startups are often filled with founders and early technical employees that are very much involved in the development. If the startup has no other revenue streams, and the development of their device is their primary concern, then you can bet they'll want to be hands-on in the process. In a collaborative style engagement, think daily interactions rather than weekly or fortnightly.

Which One For Who?

From a client's perspective it's good to know what kind of involvement you wish to have in your project from the outset. Both in terms of how much work you wish to do yourself, and which competencies you want to engage for the project. To go for a more collaborative approach will likely mean rounding up your own dream team as needed, rather than having one ready made. This means more contracts, but also much more granular control of the work scopes. This might be ideal if the main business objective is to launch The Device. However, if the main business objective is to keep production running and distributors happy, then handing the project off to someone else to manage may make much more business sense.

It is worth noting however that if a design consultancy is going to manage the project, then it does cost to have them do so. Often this means that a project lead is assigned to the job and forms the main point of contact, and then a rolling roster of other technical staff come and go as needed. You generally have little control over who does each specific bit of work. On a whole this is not usually an issue, though I have seen that if the budget gets tight more of the heavy lifting gets taken up by more junior staff that cost less to resource.

Who For Which One?

From the perspective of a consultancy, I can see why taking the managed engagement approach would make much more sense for a large or medium consultancy. Being able to get a long-term commitment from a client means that resources can be allocated more effectively and the overheads covered for a predictable amount of time. Having some visibility down the pipeline is important when there are [many] salaries to be paid. If the scope is broad as well as long it can also allow you to allocate resources from a wider range of disciplines. Being able to employ a diverse range of specialisations makes the consultancy in general a more attractive option for large and challenging projects. This is its own design niche, one that is difficult and expensive to operate in - only a few of these kinds of jobs exist, and only a few can take them on.

On the other end of the spectrum is the small consultancies. This is where I find myself, and how I come to be thinking about this whole question. While it can certainly seem desirable to land the big clients with big jobs in a managed-style engagement, bigger doesn't necessarily means better (remember I said neither is better than the other?). Being able to offer small and dynamic chunks of work to a client has its own value. Sure, the numbers might not look big by comparison but by continuing to deliver, scope after scope, can mean the total of the totals is comparable. More than that, the client is with you on the journey and will get significant value from the close collaboration. Of course, this does mean each engagement might be shorter, and the pipeline not be as long. While this is a downside to this kind of engagement, and from veterans in the industry I'm told the anxiety never goes away, the risk is reduced by keeping the overheads low. Further, small consultancies are often far more specialised. Unlike a large consultancy with a wide range of specialisations and thus diversified income streams, a small consultancy may only find income from a single type of job. Indeed, a single consultant who is an expert in a very specific niche may find themselves with both a very short and narrow pipeline.

Comparison is the Thief of Joy

The reason I've given all this as much thought as I have is because it's easy to get caught up in the numbers. How big the project is, how long it'll run for, etc. But looking retrospectively at much of the work I've done to date, it's amazing how much it all adds up. Both in terms of value to the client, and value for me. Breaking down the difference in engagement styles, and why one might work better than the other, is an important way of identifying how to better serve the needs of your clients, and your own business. There's a lot more to it if you [over]think about it.

ⓒ Lincoln Black 2024

Virmachi-Logo-White-Transparent

Virtimachi Pty Ltd

ABN 31 651 760 762

PO Box 7156 Kariong

NSW 2250 Australia