Claim OwnershipPirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
Subscribed: 0Played: 0
Subscribe
© 2026 Pirmin's Podcast : IT - ERP - Projects 33 years of experience - 99 thoughts, a weekly podcast
Description
I am the author of
"IT - ERP - Projects 33 years of experience - 99 thoughts - 66 minutes to read: Not Another How To Book"
Available on amazon (check your local amazon for faster / cheaper delivery!) or check http://www.pibeco.com/book
Some of the feedbacks I got were the wish for more details / more explications on the individual thoughts.
I'll take that challenge and will create a weekly short podcast on all major medias and video cast on YouTube.
It will be published on fridays, each episode starting with the lecture of one thought and then a brief explain / idea / experience behind. The podcasts will be 5-10 min.
If you like .. share and forward !
If you want to get in touch with me, check on LinkedIn
( https://www.linkedin.com/in/pirminbercher/ ) or via www.pibeco.com
If you liked .. spread the news !
If you can’t wait for next week www.pibeco.com/book
If you want to support me coindrop.to/Pirmin or www.buymeacoffee.com/pirmin
Have fun !
Greets
Pirmin
37 Episodes
Reverse
Hello, few months ago, I published a book on my 33 years of experience in IT - ERP -Project. Some readers requested deeper insights on the topics, so I decided to go for a pod/video cast to deeper explain. This is the introduction pod /video cast, which will be followed by a weekly cast on the individual thoughts ! It’s a fully unscripted recording ! Happy to get your feedbacks! If you liked .. spread the news ! If you can’t wait for next week www.pibeco.com/book If y...
#37 Use the best on job When it comes to the creation of the team, we need people who can do the job. Make sure that you use the best for this job from your organization! This may hurt, but only if you select the best persons you can get the best results. One mistake often done is, that the „Best in Job”, maybe the purchasing team lead, is so highly involved in the daily business, that he sends his deputy or even worse the „newbie“ in the department as the newbie does not yet support th...
#36Free the resources Make sure you can free the needed internal resources. Having critical key roles covered with people who are attributed “50% of their time” for the ERP will not work. They need to be fully attributed and committed to this critical task. Prepare the back-fill of these early enough, to make sure that the replacement person is trained well enough to support daily business. Some persons may only need to contribute to individual tasks with a small amount of time, but the...
#35 An ERP implementation is enough Typically, an ERP implementation challenges a company to its max. On the resources side manpower will be, apart from fi-nancial restrictions, critical. There will be many operational resources involved either directly with elaborating the new/adjusted business processes or indirectly by supporting the persons who too took over their business /operational work, which they did before. Also changing / implementing an ERP system requires to rework / redes...
# 34 An ERP implementation is like a heart surgery An ERP is by its straightforward meaning „Enterprise Re-source Planning“ in most cases the core system to maintain your business processes. Implementing this or deeply changing it is like an open-heart surgery. You need to be aware of the risks, the work ahead but also having the confidence that the implementation will be successful. Therefore, one of the fun-damentals is to have a team you trust and rely on. Not only on your direct reports, ...
Watch it till the end, and next time when you have breakfast, think of the complexity # 33 Give me what I want not what I asked for The typical problem is that the requirements are not clearly defined which leads to a different solution. Make sure that the persons involved in the requirements definition understand the business case, understand to communicate this requirement to different stakeholders and to abstract their problem from the direct use case. Developers think different than func...
# 32 Systems should make work easier Always keep in mind that you need to generate value with your solutions. Sounds too obvious. Not because having a fancy thing makes it a good thing. People like easy and fail proof things that don’t need too much thinking. Often, we tend to forget what the customer wants and deliver a technical solu-tion. Today there is a little mistake in it, do you find it? The first who pings me, mail via my website www.pibeco.com or here, gets a free paper copy...
Double episode ! There's no (Excel) Heaven without (Excel) Hell # 30 Excel is heaven In many companies, Excel is the wonder tool! When you look around the things that can be done by Excel, it’s sometimes amazing that there are other tools in the world. As often read, Excel is not an ERP ;). But you should not underestimate what can be done by an Excel expert. But also be sure that you are the expert or have the expert(s). # 31 Excel is hell As said before, Excel is heaven i...
# 29 Don‘t waste time in technology This is the opposite of „let technology do the job“. Sometimes we tend to make everything automated or system driven. There are cases where you need to think about it. Does it make sense to spend 2 days in preparing a data upload, testing when you only have to upload 10 records and can type this in in 1 h? Is the data cleansing more time consuming to prepare an upload file than training a human to do the job? It’s like always a fully unscript...
# 28 Let technology do the (dumb) job If you work on a complex project or complex technology, try to make the machine do the dumb jobs. There are many things that can easily be automated, trained to tools and applications. The more of the simple tasks you transfer to these little help-ers, the more time you have for the complex things. It’s like always a fully unscripted recording ! Happy to get your feedbacks! If you liked .. spread the news ! If you can’t wait for next w...
# 27 Multi sources for messaging create confusion If you use reminders / messages generated by workflow or systems, try to keep them to a needed minimum as they will sooner or later be ignored. Try also to avoid to have these mes-saged from multiple sources / different communication ways. They all look different, requesting different actions. The more you have different ones, the more likely is that a user oversees them or interpret them as a possibly unwanted message. This applies especially...
# 26 Be careful with workflows and remindersWorkflows can be a great tool to steer and control the execution of a business process where multiple people are involved. One great thing about workflows is, that the workflow engine can send messages to the persons who are in charge of the execution of the next step. Just like the „be careful with standard messages“, be careful with these. If the workflow sends a reminder to the whole finance department, maybe 10 people, to execute an invoic...
# 24 Don’t over guide Typically “assistants” or user guided processes are needed in early phases of a project. Just like a step-by-step workflow, asking you questions, guiding you or offer pre-filled values. Most of these guided processes then include drop down lists to select something and then “click ok” go to next screen. In most cases, these assistants will have a lot of explanatory infor-mation. All this is good, if a process is either executed very few times or generally, the user is no...
# 23 Digital s**t does not smell… That’s all What is the difference between analog s**t and digital s**t? The analog one sticks at your shoes and smells... on the other hand, the digital one sticks on you but doesn’t smell. If you don’t do your homework and check what goes wrong in your old way of working and seek to understand why it’s going wrong, you will just implement the old/analog way. This ap-proach is not going to solve your problem. Generations of ERPs have been implemented to impro...
# 22 Don‘t make all your processes bullet proof Don’t try to make all your processes and exceptions bullet-proof. This will only increase the complexity of the implemen-tation and complexity is the enemy of stability, budget and success. Make your few core processes tank-cannon proof! If your employees can rely that a defined standard process is working stable and predictable, they can handle the exceptions. If you also try to make your exception process bulletproof, be sure to have the resou...
# 21 Don’t try to reach everything in one run When you start your project, the ambitions and motivation to change and go for the best are high. Even if aiming for the stars is needed to achieve best results, you need to be realistic enough to focus on what is needed. You will not reach any perfect result in one shot! Create something that is working. Give the team a success. Start with a minimum viable prod-uct/project. This makes failure less likely. Be sure some people will be disappo...
# 20 Don’t change / widen your scope Even though you should be open to increase the functionality, integration or usability of a solution, don’t change the scope once the project is started! Everybody tends to change or in-crease the project scope during the implementation phase as we all are learning and seeing that what we originally defined is not sufficient. Changing / adjusting the scope should only be done if there is an immediate and massive business value in-crease which over rules t...
# 19 Aim for the stars As your business vision is a vision and may never be achieved, your project vision must be open and wide. Don’t exclude ideas or solutions at the beginning. Think about all the integra-tion possibilities or features that would be great to use. As long as you stay realistic and know that aiming for the stars may result in landing on the moon, all is good. If you block yourself too early, you may even not reach a lift off. It’s like always a fully unscripted recor...
#18Coca Cola is not Pepsi One difficult thing for people is to imagine similarity or mak-ing abstractions. A Cola beverage is mainly water, sugar (or substitute), color, flavor, CO2. (Some details missing ... don’t hate me for that). If you now discuss at Pepsi a software im-plementation where you use the (perfect) slides you made for a Coca Cola project, the audience will in 90 % of the cases complain that „We are not Coca Cola and all is different“. They can’t abstract that maki...
# 17 A partner is a partner If you choose to implement a larger software project, you should consider the role of external persons / your implementa-tion partner. Complex software implementations need a deep understanding in your business and a deep trust from you in your partners. You should consider your implementation part-ner as partner not as a vendor/contractor! Same applies for other involved persons like freelancers, developers, sub-contractors. If you integrate them in your tea...
Comments
Download from Google Play
Download from App Store
United States