Discussion about this post

User's avatar
Li R's avatar

there is a horrifying amount of undeclared methodological knowledge everywhere once you start looking. secretaries who know the bureaucracy inside and out. engineers with procedural knowledge that will be lost once they retire. artisans with techniques so specialized no one can replicate them. people with deep knowledge of social networks, who can assemble teams of people to solve almost any problem, etc. etc.

thank you for writing. i love your posts!

Bianca Schulz's avatar

You promoted me with this, because now I can argue that my work, namely reshaping organizations through methods, is actually technology. Brilliant! I am going to put this on my website right away! :-)

I am also a big fan of Lean thinking and have applied many of its principles to how teams, leadership teams, and ways of working are shaped. The workplace example can also be transferred very well to virtual workplaces in offices. There are companies that have three different apps with dozens of channels for sending messages and the communication paths are a mess, there is no visual order.

But also the way leadership is practiced could also easily be standardized and everyone could be assessed against it annually.

Industries with high risk are good examples. A few days ago I had a long conversation with a flight attendant. All procedures are trained regularly. In an escalation scenario, everyone knows what to do. That is why it works. The methods there are strictly monitored.

All organizations can take a page from that book. Naming methods as technologies is exactly the right approach. Now with AI this is becoming highly relevant again.

I think what has been a bit exhausting in recent years was the overflow of methods in offices and soon people could not stand hearing about them anymore. Everyone came along with something new. Then it was just managed half heartedly.

But I have also accompanied organizations through transformations that very deliberately chose which methods to adopt and introduced them very strictly and with discipline, and that was successful.

What I find important is that the people who want to introduce methods understand their craft.

Through your articles you can see how much knowledge and experience one needs to bring.

With many technologies the barrier is much higher, you have to be an expert. With methods you only need to be a good talker. But in practice it does not work. The barrier should be higher. If you call it a technology, you would need to describe which expertise is required for defining and introducing the method. I see more of a cross functional team that jointly develops, defines, and introduces the method.

What would be your advice to organizations when they want to introduce methods or change their organization? Who should they bring into the team and who should they not?

2 more comments...

No posts

Ready for more?