-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Initial draft of the PLG core product groups article * Fix spelling
- Loading branch information
1 parent
d7092b7
commit 9e76401
Showing
2 changed files
with
90 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
!! title: PLG - The Product Triad | ||
!! slug: plg-product-triad | ||
!! published: 2023-09-18 | ||
!! description: Examining and defining the roles of the core product triad in a PLG company | ||
|
||
--- | ||
|
||
In a PLG company, the product is at the very center of everything, with the user being the center of the product. Lean | ||
management fits extremely well with the PLG business model. Lean management looks to maximize value delivery to the user | ||
while minimizing waste. | ||
|
||
Every department, team, and individual shares the same goal of improving the product and is aligned with the lean | ||
management principles. And each one of these entities brings a unique and important perspective in this alignment and | ||
plays a specific role in the makeup of the organization. | ||
|
||
|
||
## The Core Product Groups | ||
|
||
Product owns and is responsible for the value that is delivered to the end user through the product. They are the | ||
collection point for all end user feedback. Their main responsibility is to collect all of this feedback, synthesize it | ||
to problem definition. They also lead the plan on what metrics need to be collected to verify the problem and measure the | ||
value to rank it against other problem definitions. These metrics include the supporting metrics for financial gain. No | ||
product decision, whether it leads to financial growth or not, is made without the data in support. | ||
|
||
|
||
Design owns and is responsible for designing the solution to a defined problem from Product that is deemed the highest | ||
value delivery to end users. They develop and design solutions and alternatives and run user research on them to | ||
validate their designs. If the solution is a large functionality change, the user research should be done previous to | ||
the solution being implemented in the product. However, if the solution is not a large change, the user research should | ||
come from in-product and be supported by the user feedback loop to Product. If A/B testing is applicable, it would be | ||
used here to enable in-product user feedback. Secondarily, Design uses their user experience expertise to help support | ||
Product with user data by providing user research to help measure and analyze product in support of defining user | ||
problems and prioritizing the defined problems. | ||
|
||
The primary responsibility of Engineering Development is to implement the solution that Design has developed. Their | ||
secondary responsibility is to use their technical expertise to support Design with technical review of solutions and | ||
alternatives to defined user problems. Design leans heavily on Engineering for the feasibility and complexity of a | ||
solution. Engineering is responsible for providing feedback to assist with minimizing technical complexity to contribute | ||
to the overall Lean goals of maximizing value delivery while minimizing waste. Complexity is the enemy of Lean since it | ||
causes friction in fast delivery of value by being slow to develop and test. Complexity is also risk prone to rework | ||
which increases waste. | ||
|
||
If the organization's engineering practices support a culture of experimentation and iteration, one of the important | ||
user data collection streams is in-product. Increasing the velocity of delivering a minimum valuable product into the | ||
hands of the users to gain feedback enables higher velocity of value learning. The primary business goal of a product is | ||
to delight and deliver value to the users. Feedback on already-delivered product capabilities leads to faster refinement | ||
of what is valuable to the end user: what is worth investing in and what is not. This is the secret to leading the | ||
marketplace. | ||
|
||
The organization structure should be such that it promotes PLG and lean management. The lean management principles | ||
should be applied to the communication channel creation as well: maximize the delivery of value in communication while | ||
minimizing waste of unneeded communication. Organization communication is the hardest problems to solve. [Conway's | ||
Law](https://www.melconway.com/Home/Committees_Paper.html), the [Inverse Conway Maneuver | ||
reference](https://yoan-thirion.gitbook.io/knowledge-base/xtrem-reading/resources/book-notes/team-topologies#conways-law) | ||
to the findings in [Accelerate](https://www.oreilly.com/library/view/accelerate/9781457191435/) in relation to the | ||
Inverse Conway Maneuver and the [implications of executing such a | ||
maneuver incorrectly](https://medium.com/@Cyrdup/icm-1-say-no-to-the-inverse-conway-maneuver-6672ba2373cb). | ||
|
||
|
||
--- | ||
|
||
In PLG organizations, the Core product groups each have a complimentary roles and responsibilities to play in order to | ||
be the most effective. Each business function relies heavily on each other to make up the whole of the core product | ||
group to optimize the Lean management goals: maximizing value delivery to the end user and minimizing waste. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
!! title: PLG - Support Functions | ||
!! slug: plg-product-triade | ||
!! published: 2023-09-18 | ||
!! description: Examining and defining the roles of the core product triad in a PLG company | ||
|
||
--- | ||
|
||
- Lean Management: maximizing user value while minimizing waste [https://kanbanize.com/lean-management/what-is-lean-management] | ||
|
||
- PLG Core: Product, Design, and Engineering | ||
- PLG Marketing: Marketing, Customer Success, Sales, and Product | ||
+ marketing with the product at the center with the user at the center of the product [https://www.toplyne.io/blog/plg-marketing] | ||
- PLG Finance: Finance and Product | ||
- PLG Operations: Operations and Product | ||
|
||
- product development triad | ||
+ Product answers Why | ||
+ Design asnwers What | ||
+ Engineering answers How | ||
* Development answers how it is built | ||
* QA answers how it has affected the existing product | ||
* Operations answers how it runs in production | ||
|
||
- How does Operations fit in? | ||
+ Getting feedback to Product in a way that communicates value to the end user. "Stability" and "Delivery" are going | ||
to be the key words in these conversations as well as important metrics around these areas. |