Archives: Tweets
-
@daveixd @johnmaeda @JShoee @kpcb aside from norms, the question is what should these ratios be – otherwise the norms won’t change.
-
@daveixd @johnmaeda @JShoee @kpcb well, I’ve just spent a few years at the enterprise ratio, and I’ve seen orgs at the others.
-
@johnmaeda @JShoee @kpcb ratios include specialty functions – e.g. architecture, research – implicit for smaller groups, explicit for larger
-
@johnmaeda @JShoee @kpcb that’s [_] product managers / [_] designers / [_] engineers.
-
@johnmaeda @JShoee @kpcb Rule of thumb 1:1:3 for consumer / high polish offerings – 1:2:5 for typical SaaS tools – 1:2:10 deep enterprise
-
RT @jboogie: Want to make your teams more successful? Change their names. buff.ly/1VBgCrX
-
@doriantaylor got it. Closing the loop, your all-nighters originate with structurally inflexible contracts created by non-practitioners.
-
@doriantaylor I’m pointing at the structural nature of the domain. If practitioners = people who sell & define services contracts, we agree.
-
@doriantaylor It’s not as common in my experience. Services contracts = inflexible, so people absorb the inherent uncertainties of the work.
-
@doriantaylor time to switch to product – ditch the services life 🙂