The personality of the leadership will determine whether they think of workers as self-motivated (will actively look for work) or externally motivated (will wait for work and try to avoid it). Those who don’t think workers are self-motivated will build management structures where people are discouraged from thinking beyond their station and have all kinds of reporting and incentives to make them do their work.
I was for a long time hard in the self-motivated camp, but eventually realized that’s me and not everyone, and maybe not even most people. A multi-modal management approach that leaves room for both works better but is harder to pin down.
Thanks for the info, fellow Flemish guy (your name gave it away :D)
My experience tells me you should just assume everyone is going to need the external carrot/stick arrangement.
You'll save a lot of pain by realizing that no one cares about the product as much as the people spending 14 hours a day on it.
If this communication goes wrong it can result in deaths and giant profit leaks until eventual bankruptcy.
Programming can fail much harder.
If you listen to programmers, the app has technical debt, and needs to be rewritten on [next tech stack needed on the developer’s resume]. I’ve hear that on a 6-month-old app written in SpringBoot/React in 2020.
Leader-blaming is a nice sport, but actually working together with full responsibility on both sides is a much rarer skill. Including being fired with damages if you summon KubernPyKafka in Scala and your team doesn’t produce features during 6 months.
Getting flashbacks from my own time working on what I like to call Cthulhu Architecture. KubernPyKafka in Scala is probably the most reasonable part of it.
The parts that needed to be fast were in python. The parts that could afford to be slow were in Go or LuaJIT. Ops in C++. And the parts that required well defined carefully controlled business logic to be encoded were in JavaScript if you were lucky, but more likely embedded in a DSL constructed over YAML. ACID built over top of NoSQL. Still only scratching the surface of the insanity. I’m sure there are many of us carrying these scars; some of the intent on bringing this dysfunction into their next organization.
> And finally, if users and employees can be replaced, so can companies, products and services.
Yep.
And now maybe reddit's number is up, and it's time for it join Myspace, Friendster and Twitter?!
After I worked a few years in the industry, I came to the following conclusion: The main difference between a factory and a knowledge business is that in a factory, the smartest, most knowledgable people are at the top (not completely the case, but mostly). In knowledge work, the smartest (=experts) are at the bottom. If you move up as a smart person, you will for sure lose up-to-date knowledge.
This has a few consequences of course. In knowledge work, managers should not say "First do this, then do that". Managers should be at the service of their team, making sure they get the focus and freedom to work on their stuff.
Now back to the factories: I'm no expert, but one of the key elements of Lean Manufacturing is that the people on the floor are able to provide feedback to the upper layers. Why them? Because they have the hands-on knowledge and see things management can't. So even in factories, either you listen to the lowest level employees or you're not optimising your process.
And finally, if users and employees can be replaced, so can companies, products and services. The thing is that having great retention in users saves you a lot of investment on acquiring new ones. And having great retention in employees saves you a lot of investment in hiring and training. The leaders that realise this will outperform anyone that doesn't.