I believe this also ties to the different engineering practices in Meta and in AWS as you wrote. AWS has extensive software tests whereas Meta has several staging environment to test business metrics. It may be good idea to link to them.
I believe this also ties to the different engineering practices in Meta and in AWS as you wrote. AWS has extensive software tests whereas Meta has several staging environment to test business metrics. It may be good idea to link to them.
Yicong: I'm not sure I fully follow. Yes, they do these, and so have additional layers to validate that stuff works and/or measure the impact. Do you mean that it could be helpful to mention that e.g. Meta is already measuring this business impact where they can?
Indeed, in the sense that Meta and AWS are both linking to business metrics (outcome) but what they do is different because they generate profit differently; this pair of examples show no one size fits all, in contrast to McKinsey's framework. Oh...I forgot to mention, they were from your blog, something about engineering culture maybe.
I believe this also ties to the different engineering practices in Meta and in AWS as you wrote. AWS has extensive software tests whereas Meta has several staging environment to test business metrics. It may be good idea to link to them.
Yicong: I'm not sure I fully follow. Yes, they do these, and so have additional layers to validate that stuff works and/or measure the impact. Do you mean that it could be helpful to mention that e.g. Meta is already measuring this business impact where they can?
Indeed, in the sense that Meta and AWS are both linking to business metrics (outcome) but what they do is different because they generate profit differently; this pair of examples show no one size fits all, in contrast to McKinsey's framework. Oh...I forgot to mention, they were from your blog, something about engineering culture maybe.