3 ms·
There was an interesting article about a closely related subject, but I can't find it anymore. Basically, there's a dichotomy between 2 different kinds of work
by crispyambulance 7y ago
There was an interesting article about a closely related subject, but I can't find it anymore.
Basically, there's a dichotomy between 2 different kinds of work: Convergent vs Emergent.
In "Convergent" work you are delivering what a market has asked for. You are measured on meeting these requirements with accuracy, speed, cost. Predictability of outcomes is paramount, schedules are everything, people expect to be able to control all variables.
By contrast, in "Emergent" work, you are effectively creating a market. You introduce something that hasn't existed before and which isn't merely a tweak in an existing product. The outcome of Emergent work is new ways of doing things, new products, and new resources. This introduces a lot of "grey area" and lack of focus.
The most successful enterprises find the right balance between Convergent and Emergent work. In manufacturing (my domain), most initiatives are Convergent and expectations focus on meeting some deadline or numeric goal, literally everything else is subordinate to that. Start-ups, of course, have the opposite inclination. In those, a "runway of money" is burnt to introduce some potentially new product with only vague expectations of profit at some time in the future (despite whatever they tell VC's). You sort of need both in an organization and staff (as a whole) need to assimilate both types of work to really succeed.
- tomp 7y agoThanks, that's a really useful distinctin. I've been thinking along these lines already before, but it's useful to concretely name and describe different modes of work, to better incorporate them in my mental model. What I had in mind was things like Customer Support or QA personel (which exist even in start-ups & tech companies), where the tasks are pretty clearly defined, it's easy to track progress, and it's fairly important to "do the hours" (e.g. if you need 24-hour customer support), but you can offer things like location independence (precisely because work is so easy to track). Unfortunately, however, I think that most programming work (and this probably extends to most technological work) isn't quite as easy to categorise... basically, even if your objective is 100% convergent ("our client wants this, we'll make it"), there's still different (better or worse) ways of getting to that goal, so there's still a lot of creativity/decisionmaking involved... and it's obvious that simple metrics don't really work ("I fixed 100 bugs today!" "Yeah but you wrote all of them yesterday.")...