The Holy Trinity of Product Development
Join the DZone community and get the full member experience.Join For Free
not only is it hard to attract talent to your startup (know any free developers in the bay area?), as a founder you also have to set the proper structure. a common saying is that you need a “hacker, hustler, and a hipster” on the founding team. in the earliest days that makes sense, especially when you are mvping and hustling for your first customers trying to find a product-market fit.
sometime after you have product-market fit and raise a round of funding, you need to hire outside of the core founding team. a lot of founders struggle with the right roles to hire and what the proper structure should be. some founders hire too many engineers (typically non-technical founders) and some founders hire too many “business” or “marketing” people (typically technical founders), leading to being lopsided in one area. founders run the risk of being engineering centric or marketing centric in their product development. in reality they need to be customer centric and embrace the holy trinity of product development.
the holy trinity of product development: dev lead, pm, pmm
when it comes to product development, you need three distinct roles. those roles are what i call the holy trinity of product development: developer lead, program manager (pm), and product marketing manager (pmm). these three roles work together to represent the customer and build the business, ensuring that you are not too engineering focused or too marketing focused. the role in the middle of that fine line is the program manager.
program manager (pm)
what is amazing about the pm is that they have no power or authority over the pmm or dev lead, all they can do is influence the engeneering and marketing teams. it takes a unique skill set to get this done.
the dev lead has a difficult role to play insofar as they have to represent the engineering team to the pm and pmm as well as work on all of the “tech stuff.” the tech stuff includes: setting the development architecture, get their devops game on by organizing the build (doing things like continuous integration and continuous deployment ), coding, and choosing the right technology for the job (rails or php anyone?) the dev lead also needs to keep the engineering team together and motivated and make sure that the agile process is, well, agile.
the hardest part of the dev lead’s job is interfacing with the pm and pmm. the nature of startups is that they are resource constrained and always in a rush to get something shipped. that means an insane amount of pressure on the engineering team. it is the dev lead’s responsibility to work with the business (pm and pmm) in order to set realistic deadlines and proper expectations, all while not being the guy complaining about lack of resources. not always an easy task..
product marketing manager
while the dev lead represents the engineers and the pm represents the customer, the pmm represents the business. while the pmm is responsible for what all non-marketing people think of as marketing (ad campaigns, trade show booths, email blasts, product placement, media placement, etc), they are also responsible for the business model of the product and making sure that the product makes money (or reaches its broader goals if it is a loss leader.) this means setting pricing, and if this is a freemium product, that is far more complex than you can ever imagine. the pmm is ultimately accountable for the product making money.
the right balance
some startups and companies are tempted to combine the pm and pmm role. this is bad ! what happens when you combine these roles is that the focus usually becomes either too customer centric or too marketing centric; you need two people and two distinct roles to prevent this from happening. the right structure creates the right environment. the right people in the wrong structure is a waste of talent, they will not be able to use all of their talents, they will spend too much time fighting the incorrect structure. no amount of free massages, free lunches, and unlimited cookies will fix an improper structure. (actually it is google, facebook, linkedin, etc who have pioneered the holy trinity in silicon valley. they adapted it from the larger tech companies such as microsoft in the 1990s.)
the right people in the right structure/environment is where the magic happens.
this may sound like a lot of overhead, however, you are probably doing this in some form already. typically at the early stage, founders take on these roles and hire people to pass them off to. it’s a sign that your startup has matured and left the experimental phase.
now go and build awesome products!
Published at DZone with permission of Stephen Forte, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.