The tool shall follow the process, not the process the tool
Rainer Sturm / pixelio.de

The tool shall follow the process, not the process the tool

Again, and again you enter companies, where - of course - for years - everything has been "built around the tool". The tool is, therefore "set by management" and now carved in stone and not changeable

Who has the lead?


Everyone would say that the process (what do I want) takes the lead and that the tool has to follow the process.

Most of the processes that you find in companies are often old or, in my opinion, even worse, built around the tool that has been in use for years.

Apart from the fact that there are tools that are so bad that employees just quit because the company does not change the tool, designing the processes around the tool is the wrong thing to do.

This type of approach to building the processes around the tool was certainly opportune 20 or 30 years ago. However, those who want to succeed in the market today need procedures that increase their strengths and minimize their weaknesses.

Changerate

Technologies have gained a rate of change or self-dynamics, which is very high.

Today many office tools (such as Excel) are being used in ways that may have been appropriate in 1995 but are now outdated.

"This is the tool of choice to do it all."

However, the sheer quantity of information flowing in daily causes restrained or anxious behaviours at the decision maker level. To protect themselves in the decision, large companies often use consultants, at least if they are larger companies, the mid-sized or small companies can not afford these consultants.

(And even then, it is not the case that the solution hoped for by the market leaders or consultants achieves the desired result)

The technology is not implemented


This situation of the high rate of change, coupled with a mostly thin capital and sometimes even the aversion to new and, and, and leads, especially in the backbone of the economy (the middle sized companies) to the fact that new and improved technologies, methods and processes are not even used. Even if there is a need for change, existing procedures and tools are not changed. (it has worked so far.)

The results of the new often do not even reach the mid-sized companies.

Of course, every day, the pressure on the decision makers increases to do something finally, so you do not lose the connection to the technology.

From all sides, the decision-makers are influenced, to decide, use the latest technology, the most recent processes or the latest methods.

Last but not least, the decision maker will do something because of the massive pressure he is experiencing deciding for "the new one". 

But this decision is usually born out of the pressure and is (unfortunately) almost always without a real (technical) reason.

Large companies have the opportunity in pilot projects to try out to what extent new technologies, processes or methods can help the company, especially medium-sized companies are often denied this opportunity.

What is "the best"?

No matter what new methods I met, they were, and that includes agile development, only: "New wine in old tubes".

So far, nobody has been able to explain logically to me where the contradiction between agile development and the classical known development methods and processes exists. Nevertheless, this method vehemently advocates agile development and agile methodology as "the best sow in the village".

That the change to an "agile organization" takes 7-8 years, is often concealed.

Of course, agile development is all about software, too.

More Insights.

A study on the best way to develop software, which in my opinion is fully transferable to other methods and developmental processes, concludes:

The selection of a development method (added by the author of a development process) nothing to do with a technical decision. It is more about the approach of joining a religious cult. 

These findings of this study for sure do are not transported by the consultants to their clients, because, doing so would reduce their revenue.

Processes

Every business, every human being has some process. No matter if it is brushing your teeth or eating or sleeping. Everything can be viewed as a process in this sense. Moreover, almost everyone has a different method of doing this.

As mentioned above, due to the tremendous pressure that someone is experiencing, very often well-tried things are thrown overboard.

Processes are not set in stone, and an adaptation of the processes is daily bread.

Mobile phones and the so-called apps did not exist 15 years ago, as they exist today. Messenger services - 15 years ago they would have received more than 37 question marks.

Processes that are ideal for your direct competitor may not be absolutely applicable in your business.

The same applies to the methods used and the tools used.

That, what leads to the desired result - exactly that

Exactly that, what leads to the desired result in your company is what is "right".

There are companies that, after losing 30% of their workforce in one year, find that "We are the best company, and if anyone goes, it can only get worse. " This statement is made, of course, while the management has ignored significant suggestions for improvement and the company gets more and more problems every day.

The above will not lead to the desired result!

So far, I have told every employee who has been confronted with such or similar situations that he should leave this company as soon as possible because the management is riddled with idiots or led by idiots.

The process (WHAT DO I WANT) has the lead.

Precisely this question is answered with a process.

The realization of this process, how do I do it is described with the methods. Finally, the question comes "With what?".

Which tool is the right one?

Who assumes the leadership role, and who is the successor is answered extremely clearly with this point.

The tool must be able to follow my process; otherwise, I do not need the tool!

Summary

Take the leadership role in your company's processes and demand their effective implementation. (This is one of the main tasks according to ISO 9001)

If you decide to use any tool/software tool, do so, but do it based on technical requirements that apply in your business.

I repeat Technical requirements!

Make sure that the tool can map the company processes that you or your employees are responsible for.

Be energetic, even towards a big company.

Also, above all, one thing:

Be successful!


要查看或添加评论,请登录

Thomas Arends的更多文章

社区洞察

其他会员也浏览了