Talk:Main Page: Difference between revisions
Adietrich13 (talk | contribs) No edit summary |
(→Features, Tech Debt, and Security, Oh my!: new section) |
||
| Line 2: | Line 2: | ||
<comments/> | <comments/> | ||
== Features, Tech Debt, and Security, Oh my! == | |||
= Everyone Loves You! = | |||
Can you have too many customers? A business cannot succeed without customers, but what happens when they want more of your time, energy or services than you can offer? Even worse, what happens if your customers each have a very reasonable request but the number of requests is untenable? That could spell disaster. Who hasn't had a million things on their plate and had something small fall off of it? "Hey, I asked you to do the dishes and you said you could, but you didn't. What gives?" That situation sucks. It's bad whether the cost is a bit of harmony at home lost because someone was let down, or because your boss is upset because "setting up that meeting wasn't a huge ask", or a customer said "All I needed was a small change", or "My order wasn't complicated." | |||
So what do we do about it? As an individual, a team, a product, or an entire enterprise capacity cannot expand infinitely. Some would argue that capacity is fixed and at any given point in time it is. Sure, it can be scaled over time and an individual's capacity changes based on other circumstances but at a single point in time, when a request is made capacity is fixed. So what do we do about it? Demand is outpacing supply! Oh no! Our in demand commodity is scarce, in the short term you charge a premium, which is good, but if you can't scale up you're headed for trouble because people tend to get upset when they don't get what they want, especially if they paid for it. | |||
== Managing Multiple Intake Streams == | |||
I think I've painted enough of a picture so let's dive in. Let's pretend, you're the managing vast enterprises. You're the head of product for a software company that provides a service that people just can't live without. You've got business development talking about new opportunities, engineering talking about tech debt, there's quality concerns, automation, security says you need to make changes to meet some compliance standards, customers are demanding new features, there are industry set deadlines that you can't move, HR says it's time for annual reminder training, those Agile people say your teams need to do things differently and on top of that you're a benevolent leader so you want to give your people time to be [https://www.danpink.com/2011/07/how-to-deliver-innovation-overnight/ creative] and develop themselves professionally and personally. How do you meet all that demand? | |||
To be continued... | |||
#value #product #intake #priority | |||
Revision as of 11:09, 27 April 2023
Let's create this new page for awesome and cool discussions. No dum dums here.
<comments/>
Features, Tech Debt, and Security, Oh my!
Everyone Loves You!
Can you have too many customers? A business cannot succeed without customers, but what happens when they want more of your time, energy or services than you can offer? Even worse, what happens if your customers each have a very reasonable request but the number of requests is untenable? That could spell disaster. Who hasn't had a million things on their plate and had something small fall off of it? "Hey, I asked you to do the dishes and you said you could, but you didn't. What gives?" That situation sucks. It's bad whether the cost is a bit of harmony at home lost because someone was let down, or because your boss is upset because "setting up that meeting wasn't a huge ask", or a customer said "All I needed was a small change", or "My order wasn't complicated."
So what do we do about it? As an individual, a team, a product, or an entire enterprise capacity cannot expand infinitely. Some would argue that capacity is fixed and at any given point in time it is. Sure, it can be scaled over time and an individual's capacity changes based on other circumstances but at a single point in time, when a request is made capacity is fixed. So what do we do about it? Demand is outpacing supply! Oh no! Our in demand commodity is scarce, in the short term you charge a premium, which is good, but if you can't scale up you're headed for trouble because people tend to get upset when they don't get what they want, especially if they paid for it.
Managing Multiple Intake Streams
I think I've painted enough of a picture so let's dive in. Let's pretend, you're the managing vast enterprises. You're the head of product for a software company that provides a service that people just can't live without. You've got business development talking about new opportunities, engineering talking about tech debt, there's quality concerns, automation, security says you need to make changes to meet some compliance standards, customers are demanding new features, there are industry set deadlines that you can't move, HR says it's time for annual reminder training, those Agile people say your teams need to do things differently and on top of that you're a benevolent leader so you want to give your people time to be creative and develop themselves professionally and personally. How do you meet all that demand?
To be continued...
- value #product #intake #priority