Member-only story
Why Truly Multidisciplinary Teams Can Lead to Building Better Products
Every discipline needs a seat at the table
Imagine yourself as a software architect or tech lead, and a project manager brings you in to a new software project.
She describes the client and the problem they want to solve, and it definitely seems to be an interesting project. It’s for an exciting brand in a very interesting space, and it would likely leverage some exciting technology.
You’re looking forward to being part of the team which will bring it to life.
“Cool!” you tell the PM. “Let’s get started. When’s the kick-off meeting? It will be great to meet with strategy, design, and the client to start talking about what we want to do here.”
“Well,” she replies. “That’s already happened. We kicked things off six weeks ago. We’ve already identified what the product needs to do. We have some designs we’ve been testing with users, and we’re just about ready to hand the finished designs over to your engineering team so we can deliver an MVP in two months.”
You’re incredulous, but you’ve unfortunately seen this before. You sigh. “Okay. Tell me more about what this does and then show me the designs.”
