Knowledge gained from a completed project is priceless

Article#: 00071

Date: 2021-10-27

Author: Radim

It's not just about a good vision, a good plan and a good concept, we also have to implement and complete the project (successfully) and learn from it.
The knowledge gained from a completed project is priceless.
The course of the project shows how well the project was planned and managed.
Do we meet the installation deadline and budget?
Have all the important requirements been met?
Can we carry out the commissioning smoothly and on schedule?

The learning does not end with the commissioning of the machine and the handover to the customer. The real result of our efforts remains to be seen.
How satisfied is the customer with the system?
Does he enjoy working with the system?
Does the machine produce good quality with minimal downtime?
In an event of an error, is it easy to determine the cause and correct the error?
Are requirements for additional features easy to implement?

© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).

Related previous articles:

• Machine modularization
• Modular software architecture
• Hardware concept
• A good concept = Complete set of suitable solutions
• Are there also any disadvantages?
• Think critically!
• Design machines with a focus on user's abilities and needs
• Learn from your journey!
• Project leader
• Why do automation projects fail?
• Collect all the requirements and sort them!
• Who will operate?
• Functional and intuitive HMI
• Use a usefull styleguide!
• Write and accept only readable code!
• Write down your best practices and processes!
• HMI and PLC applications should grow together
• Prepare a good project plan and keep it up to date!
• Is the way really the goal?
• Do you really want to start with this?
• I can see what you can not see
• More than just start and stop
• Safety first!
• Do the right things and do them right!
• Define test scenarios and test cases continuously!
• Don't make it worse!
• Write a project diary!
• Keep the answers to the question "Why"
• Everything is difficult until it becomes easy
• Realize every good idea ASAP!
• Get and stay in the flow!
• Industrial evolution - Listen to your customers and follow new trends!
• Stay alert!
• What does the customer need?
• Don't disappoint your customer!
• Ask questions!
• Communication skills are extremely important
• Don't replace employees in the middle of the project!
• Develop a sense of responsibility!
• Get the things done with a small, motivated team!
• Focus on target!
• Avoid overly optimistic estimates!
• Don't hide any problem!
• Check the result!
• Keep it simple!
• Don't leave a work package half-finished!
• Success is not a matter of coincidence
• Good communication is important
• Development is evolution
• Follow the vision!
• Don't neglect and don't skip any step!
• Transparency and reliability
• From an idea to a consistent system

Related next articles:

• Safety relays versus safety PLC
• Software update
• Design considerations for effective HMIS
• Clear signals
• Talk to operators
• It doesn't work without sensors
• Event logger as the very first function implemented in the program
• Diagnostic tools
• My boss was a hero
• Version control system
• High Performance HMI
• An irreplaceable employee
• HMI is not a web page
• The false illusion of rapid progress

Comment#: 00001

Date: 2021-10-27

User: Radim

"Yes, you did a ton of things wrong on this project. But you also did a ton of things wrong that you don't know about yet.
And there's no other way to find about what those things are until you ship this version and get it in front of users and customers."
- Jeff Atwood. Hyperink (2012). Effective Programming: More Than Writing Code.

Comment#: 00002

Date: 2021-10-28

User: Radim

"Success is rarely determined by the quality of your ideas. But it is frequently determinde by the quality of your execution."
- Jeff Atwood. Hyperink (2012). Effective Programming: More Than Writing Code.

Comment#: 00003

Date: 2022-06-03

User: Radim

Unfortunately, people from successful teams get ripped off and thrown into "firefighting" tasks. This means that successful teams with less and less capacity will achieve less and less further success.

Comment#: 00004

Date: 2022-10-22

User: Radim

"What do you really learn from mistakes? You might learn what not to do again, but how valuable is that? You still don’t know what you should do next.
Contrast that with learning from your successes. Success gives you real ammunition. When something succeeds, you know what worked - and you can do it again. And the next time, you’ll probably do it even better.
Failure is not a prerequisite for success. Success is the experience that actually counts.
That shouldn’t be a surprise: It’s exactly how nature works. Evolution doesn’t linger on past failures, it’s always building upon what worked. So should you."
- Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.

Comment#: 00005

Date: 2022-10-01

User: Radim

"Everyone has a plan 'till they get punched in the mouth."
- Mike Tyson

Comment#: 00006

Date: 2022-11-30

User: Radim

New problems occur in real operation that were not expected or experienced during development or test operation.
Then you are happy if you know the system / devices well, if you know how they work, how they are connected and controlled, etc. This know-how comes simply from working on the system, from solving smaller and larger problems...

Comment#: 00007

Date: 2022-11-30

User: Radim

During development, do not use other (preliminary) hardware than the one selected for production. You gain important experience with the hardware. You will find out whether the performance is sufficient and learn how to eliminate problems that arise during development. If the software development phase is carried out on the hardware designed for sharp operation, you will experience fewer unpleasant surprises after the machine is commissioned.

Comment#: 00008

Date: 2022-12-12

User: Radim

It's easy to give advice at the beginning of a project. Everyone here knows best. But are these consultants able to bear the consequences of a failed development that lasts for years and cannot reach satisfaction?

It is usually experienced people who are not asked for their opinion when a concept is being defined, but who repeatedly have to struggle with the consequences of wrong decisions, workarounds and fixes due to the fact that conceptual decisions were not made based on experience.

⇒ Involve experienced people in conceptual decisions and thus avoid later problems.
⇒ Hold people accountable for their decisions and actions!

Comment#: 00010

Date: 2023-08-11

User: Radim

"How to eliminate fifty percent of your business worries.

Everyone who wishes to present a problem to me must first prepare and submit a memorandum answering these four questions:
1. What is the problem?
2. What is the cause of the problem?
3. What are all the possible solutions of the problem?
4. What solution do you suggest?

My associates rarely come to me now with their problems. Why? Because they've discovered that in order to answer those four questions, they have to get all the facts and think their problems through. And they've done that, they find in three-fourths of the the cases they don't have to consult me at all because the proper solution has popped out like a piece o fbread popping up from an electric toaster. Even in those cases where consultation is snecessary the discussion takes about one-third of the time formely required because it proceeds along an orderly, logical path to a reason conclusion."

- Dale Carnegie. Crescent News (1944). How to Stop Worrying and Start Living.
- https://www.youtube.com/watch?v=fKzlc_N2yxw (01:07:50 - 01:09:53)

Comment#: 00011

Date: 2023-08-11

User: Radim

"Basic techniques in analysing worry:
Rule 1 - get the fact. Half the worry in the wold is caused by people trying to make decisions before they have sufficient knowledge on which to base a decision.
Rule 2 - after carefully weighing all the facts come to a decision.
Rule 3 - once a decision is carefully reached, act, get busy carrying out your decision and dismiss all enxiety about the outcome.
Rule 4 - when you or any of your associates are tempted to worry about a problem, write out and anser the following questions:
a) What is the problem?
b) What is the cause of the problem?
c) What are all possible solutions?
d) What is the best solution?"

- Dale Carnegie. Crescent News (1944). How to Stop Worrying and Start Living.
- https://www.youtube.com/watch?v=fKzlc_N2yxw (01:12:50 - 01:13:50)

Comment#: 00012

Date: 2023-08-17

User: Radim

Why is there never enough time to do it right the first time, but always enough time to do it over?

"The saying "There's never enough time to do it right the first time, but always enough time to do it over" reflects a common observation about human behavior and project management. It suggests that people often rush through tasks or projects initially, hoping to save time and effort, but end up making mistakes or producing subpar results. As a result, they eventually need to invest more time and resources to fix those mistakes or redo the work properly.

There are several reasons why this phenomenon occurs:

1. Underestimation of Complexity: People might underestimate the complexity or difficulty of a task or project at the outset. This can lead to inadequate planning and allocation of resources, resulting in mistakes or oversights.

2. Pressure to Meet Deadlines: There is often pressure to complete tasks or projects quickly to meet deadlines. This can lead to shortcuts being taken or important steps being skipped in the interest of saving time.

3. Lack of Attention to Detail: When rushing through a task, individuals might not pay enough attention to details, leading to errors that require corrections later.

4. Overconfidence: Sometimes, people might overestimate their abilities or knowledge, leading them to believe they can complete a task quickly without proper preparation or diligence.

5. Incomplete Information: In some cases, tasks or projects might be started without having all the necessary information or requirements. This can lead to incorrect assumptions and decisions.

6. Limited Resources: Constraints on resources such as time, money, or manpower might force people to cut corners initially, with the intention of fixing things later when more resources are available.

7. Learning Curve: Sometimes, tasks involve new skills or technologies that individuals need to learn along the way. Initial attempts might be suboptimal as people are still acquiring the necessary expertise.

The saying serves as a reminder that investing the necessary time and effort upfront to do a task properly can save more time and resources in the long run. Proper planning, attention to detail, and thorough execution can help prevent mistakes and the need for redoing work.

However, it's worth noting that the saying is not universally true. In some cases, rushing through tasks might yield acceptable results, and redoing work might not be necessary. It all depends on the nature of the task, the level of expertise involved, and the specific circumstances."

- https://chat.openai.com (Why is there never enough time to do it right the first time, but always enough time to do it over?)

Comment#: 00013

Date: 2023-09-06

User: Radim

What does the customer need?

"Understanding what a customer needs is a fundamental aspect of providing good customer service and delivering products or services that meet their expectations. Customer needs can vary depending on the context, industry, and individual preferences, but they generally fall into several categories:

1. Basic Needs: These are the essential requirements that customers expect to be met. For example, if someone is buying a smartphone, their basic needs might include making calls, sending texts, and accessing the internet.

2. Functional Needs: Functional needs go beyond the basics and encompass the specific features or capabilities that customers are looking for. In the smartphone example, this could include a high-quality camera, long battery life, or a specific operating system.

3. Emotional Needs: Customers often have emotional needs tied to their purchases. They may want to feel a sense of belonging, prestige, or security when buying a product or service. For instance, luxury car buyers may seek a sense of status and prestige.

4. Convenience: Many customers value convenience. This can include factors like ease of purchase, user-friendliness, and accessibility. E-commerce websites, for instance, need to be easy to navigate to meet this need.

5. Price and Value: Customers often want to get good value for their money. They may prioritize finding products or services that offer a balance between quality and affordability.

6. Customer Support: Excellent customer service and support are essential for addressing customer needs. Prompt responses, helpful information, and problem resolution are key components.

7. Customization and Personalization: Some customers value products or services that can be tailored to their specific preferences. This could include personalized recommendations on an e-commerce site or customizable software settings.

8. Quality and Reliability: Many customers prioritize quality and reliability. They want products that work as expected and are built to last, reducing the need for repairs or replacements.

9. Sustainability and Ethics: An increasing number of customers are concerned about the environmental and ethical impact of their purchases. They may seek products or services that align with their values in terms of sustainability and social responsibility.

10. Feedback and Input: Customers also need a way to provide feedback and input, whether it's to express concerns, make suggestions, or report issues. This helps companies improve their offerings.

To understand what a specific customer needs, it's crucial to engage in effective communication, actively listen to their requirements, ask clarifying questions, and gather feedback. This can be done through surveys, focus groups, customer interviews, or simply by interacting with customers in the course of business. Meeting these needs is key to building customer loyalty and growing a successful business."

- https://chat.openai.com (What does the customer need?)

Comment#: 00014

Date: 2023-09-15

User: Radim

Complaints and identified problems are good sources of innovation.

Comment#: 00015

Date: 2023-09-27

User: Radim

"By continuously improving the design of code, we make it easier and easier to work with.
This is in sharp contrast to what typically happens: little refactoring and a great deal of attention paid to expediently add new features.
If you get into the hygienic habit of refactoring continuously, you'll find that it is easier to extend and maintain code."

- Joshua Kerievsky. Addison-Wesley (2004). Refactoring to Patterns.

Comment#: 00016

Date: 2023-10-02

User: Radim

How to get the right intuition?

"Developing and honing your intuition can be a valuable skill, but it's important to remember that intuition is inherently subjective and can't always be "right" in an objective sense. However, you can work on improving the accuracy and reliability of your intuition by following these tips:

1. Increase Your Knowledge and Experience: The more you know about a particular subject or domain, the better your intuition is likely to be within that area. Gain expertise and experience through study, practice, and exposure.

2. Trust Your Gut: Pay attention to your gut feelings or initial impressions. Sometimes, your subconscious mind processes information faster than your conscious mind, leading to intuitive insights. Don't dismiss these feelings outright; give them consideration.

3. Practice Mindfulness: Mindfulness meditation can help you become more aware of your thoughts and feelings. This self-awareness can improve your ability to recognize and trust your intuition.

4. Keep a Journal: Maintain a journal where you record your intuitive hunches and the outcomes. Over time, this can help you assess the accuracy of your intuition and learn from your experiences.

5. Seek Feedback: Discuss your intuitive insights with trusted friends, mentors, or colleagues. They can provide valuable perspectives and help you refine your intuition by offering feedback on your decisions.

6. Validate with Data: When possible, seek out data or information that can confirm or refute your intuitive impressions. This can help you develop a more evidence-based form of intuition.

7. Relax and Clear Your Mind: High-stress levels or a cluttered mind can cloud your intuition. Engage in relaxation techniques like deep breathing, meditation, or progressive muscle relaxation to clear your mind and enhance your intuitive abilities.

8. Ask Open-Ended Questions: When facing a problem or decision, ask yourself open-ended questions and let your mind wander. This can stimulate creative and intuitive thinking.

9. Learn from Mistakes: Embrace your intuition's imperfections. When your intuition leads you astray, use those experiences as learning opportunities. Analyze what went wrong and adjust your intuition accordingly.

10. Practice Patience: Sometimes, intuition needs time to develop. Don't rush your decision-making process if you're unsure. Give yourself the space to allow your intuition to emerge.

11. Combine with Analysis: Balance your intuition with analytical thinking. For important decisions, use your intuition as an initial guide but then follow up with critical analysis and data-driven assessment.

12. Cultivate Emotional Intelligence: Understand and manage your emotions effectively. Emotional intelligence can enhance your ability to perceive and interpret your own and others' emotional signals, which can inform your intuition.

Remember that intuition can vary from person to person, and it's not always infallible. It's a skill that you can refine over time, but it's also important to recognize its limitations and use it as a complementary tool alongside rational thinking and evidence-based decision-making when appropriate."

- https://chat.openai.com (How to get the right intuition?)

Comment#: 00017

Date: 2023-10-04

User: Radim

"Never discourage anyone who continually makes progress, no matter how slow."
- Plato

Comment#: 00018

Date: 2024-03-25

User: Radim

Remove the "ballast" from the program!

Only include things in the program that are really needed. Unnecessary parts of the code in the program become obsolete, untested, raise unnecessary questions and are a source of ambiguity.

Sometimes it is a good idea to try more than one way in practice to find out which way is the best. However, once we have decided on a particular approach, it is important to consolidate our methods and remove the outdated ones. By removing "ballast" from the program, we eliminate potential sources of confusion and improve the overall quality of the code.