I agree, but I´d like to question the "good"-part. I think we mean the same, but in my opinion it would be more on target to call it "depth of function". Example:
It´s okay that something is delayed = the solution are worked slow, but still has to be good (quality). Burn rate it slower, but probably when the invoices are summed up (when finished finished later) its probably the same expense if the result (good) should be the same.
If "good" --> "depth of function" you end up more with something that works within the diagram. A simpler version is planned, so the scope is restricted (not so complex) and harder prioritized. This should be faster, cheaper but the solution is still with a good quality for what was planned.
If you work as a designer my thoughts might not change that much, this model that I find very helpful (thank you!). But when you use this as a model when explaining to a stakeholder it could be more effective to level out specific functionality instead of using generic terms as "good".
I guess concept-tools are like word-tools: The bigger your vocabulary the more effective you can be.
Scott, in your design book, I like when, rather like today, you talk about (what I call) the "human factor" in organizations, since I must have been off playing hooky or something when we took "street smarts" and "office politics" in high school.
Really glad I came across this post—it’s such a great way to ground conversations. Burnout from overcommitment is something I see often in the field, and this serves as an excellent, easy-to-digest resource for designers. Whether you’re self-employed or working in a corporate setting, this is a valuable tool for establishing boundaries and driving more productive, realistic discussions.
Thanks Cristian. I think any manager that wants to avoid burnout for their team knows about this, or approximates it in how they handle workload. But sadly there are many bad managers out there.
This is one of those essays that speaks to all design worlds. Your world of UX/ software design. My husband’s world of software for manufacturing. My world of residential interior design. Ideas and expertise amount to little without that special sauce of knowing how to guide clients through a process to get them where they think/want to go.Leading discussions about possibilities and trade offs is itself a creative act.
I agree, but I´d like to question the "good"-part. I think we mean the same, but in my opinion it would be more on target to call it "depth of function". Example:
It´s okay that something is delayed = the solution are worked slow, but still has to be good (quality). Burn rate it slower, but probably when the invoices are summed up (when finished finished later) its probably the same expense if the result (good) should be the same.
If "good" --> "depth of function" you end up more with something that works within the diagram. A simpler version is planned, so the scope is restricted (not so complex) and harder prioritized. This should be faster, cheaper but the solution is still with a good quality for what was planned.
If you work as a designer my thoughts might not change that much, this model that I find very helpful (thank you!). But when you use this as a model when explaining to a stakeholder it could be more effective to level out specific functionality instead of using generic terms as "good".
Thank you!
I guess concept-tools are like word-tools: The bigger your vocabulary the more effective you can be.
Scott, in your design book, I like when, rather like today, you talk about (what I call) the "human factor" in organizations, since I must have been off playing hooky or something when we took "street smarts" and "office politics" in high school.
Really glad I came across this post—it’s such a great way to ground conversations. Burnout from overcommitment is something I see often in the field, and this serves as an excellent, easy-to-digest resource for designers. Whether you’re self-employed or working in a corporate setting, this is a valuable tool for establishing boundaries and driving more productive, realistic discussions.
Thanks Cristian. I think any manager that wants to avoid burnout for their team knows about this, or approximates it in how they handle workload. But sadly there are many bad managers out there.
This is one of those essays that speaks to all design worlds. Your world of UX/ software design. My husband’s world of software for manufacturing. My world of residential interior design. Ideas and expertise amount to little without that special sauce of knowing how to guide clients through a process to get them where they think/want to go.Leading discussions about possibilities and trade offs is itself a creative act.