User:

Log in user:

(step 1 of 2)


Write your email address in the white field and then click the "Confirm" button.

Log in user:

(step 2 of 2)


Write your password in the white field and then click the "Confirm" button.
Or click the "Request password" button to request forgotten password.

Log in user - Failure:


Email address has not been found!
Click the "Previous step" button to to enter your email address again.
Or click the "Register user" button to register your email address.

Log in user - Failure:


Pasword does't match!
Click the "Previous step" button to enter the password again.
Or click the "Request password" button to request forgotten password.

Request password:

(step 1 of 2)


Write your email address in the white field and then click the "Confirm" button.

Request password:

(step 2 of 2)


Your password has been sent to your email.
Please also check your spam folder.

Request password - Failure:


Email address has not been found!
Click the "Previous step" button to enter your email address again.
Or click the "Register user" button to register your email address.

Register user:

(step 1 of 5)


Write your email address in the white field and then click the "Confirm" button.

Register user:

(step 2 of 5)


Registration code has been sent to your email.
Please also check your spam folder.
Copy the registration code from your email in the white field and then click the "Confirm" button.
Or click the "Previous step" button to request the registration code again.

Register user - Failure:


Email address already exists!
Click the "Previous step" button to enter the email address again.
Or click the "Log in user" button to log in with your email address and password.
Or click the "Request password" button to request forgotten password.

Register user:

(step 3 of 5)


Set your user name in the white field and then click the "Confirm" button.

Register user - Failure:


Registration code does't match!
Click the "Previous step" button to enter the registration code again.

Register user:

(step 4 of 5)


Set your password in the white field and then click the "Confirm" button.

Register user - Failure:


User name already exists!
Click the "Previous step" button to set another user name.

Register user:

(step 5 of 5)


User has been successfully registered.
Click the "Log in user" button to log in.

User settings:

User settings:


Please log in to be able to open user settings.
Click the "Log in user" button to log in with your email address.
Or click the "Register user" button to register your email address.

User settings:


Your subscription has been successfully canceled.

User settings:


Your subscription has been successfully established.

Write comment:

Write your comment in the white field and then click the "Add comment" button.

A good concept = Complete set of suitable solutions



Puzzle pieces

We have collected a complete set of all the necessary requirements. So we know what to do and why.

In the next step we have to find out how to meet the requirements. We are looking for solutions.
As we found the complete set of requirements, we also need to find a full set of suitable solutions that meet all of the requirements.

One solution can either meet a part of the requirement or an entire requirement or even several requirements.
Write down which requirement or requirements are met by which solution.
Think about and write down the expected impact of the solution on the requirements.
Also, think about it and write down how each solution will be tested and what criteria for success must be met.

We can find several alternative solutions that meet better or not so well the requirements.
The alternative solutions should therefore be described in terms of their advantages and disadvantages so that we can choose and apply the best solution from all the alternatives.
We should also try to estimate the time and cost of the solutions.

Some solution may be dependent on another and can only be implemented when the other solution has already been implemented.
The dependency of the solution on another must be taken into account and noted.
This is helpful when we plan the order in which the solutions will be implemented.
And before we decide not to implement a solution, we should see if another solution does not depend on it.

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


Related previous articles:


Related next articles:


The solutions table can contain following columns:
(Columns with information on each solution.)
1. Date of editing
2. Solution index
3. Solution title
4. Solution description (What and How)
5. Necessary prerequisite (Solution indexes)
6. Affected requirements (Requirement index)
7. Expected impact of the solution on requirements
8. Test description & success criteria
9. Advantages of the solution
10. Disadvantages of the solution
11. Effort [man-days]
12. Other solution costs
13. Solution request (No / Yes)
14. Solution request information: date, person, comment (why Yes or No?)

Define measurable and achievable test criteria.
Avoid using unachievable absolute criteria such as 100% reliability or 100% availability.

It is often good to imagine that the project is not limited by anything and that it is being built on a green field without having to pay attention to any limits.
This will bring our thoughts on a solution that would be ideal.

And then it is necessary to take the given boundary conditions into account and to create a model with these boundary conditions.
But we can be inspired by our ideal model.

We will probably always have to choose between more possible solutions.
A model of an ideal project can help us make decisions on a project with constraints.

"One of the most interesting aspects of smart manufacturing is how much creativity plays a role; the limitation of what can be done is based on the imagination of the individual or the organization instead of the technology. Technology is no longer the barrier."
- https://blog.isa.org/how-to-improve-quality-with-industry-4.0

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!

"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)

"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)

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?)

Does it make sense to think about digitalization if we don't see any use case?

"If you don't see any practical use case or clear benefit for digitalization in your specific situation, it may not make sense to pursue it blindly. Digitalization should always align with your organization's goals and needs. Here are some considerations:

1. Assess Business Objectives: Start by identifying your organization's objectives and challenges. Digitalization should align with your strategic goals, whether it's improving efficiency, reaching new markets, enhancing customer experiences, or reducing costs.

2. Customer Demands: Consider whether your customers or clients expect or would benefit from digital solutions. If there's no demand for digital services, investing in them may not provide a return on investment.

3. Competitive Landscape: Analyze your competition. If your competitors are effectively utilizing digital technologies to gain a competitive advantage, it might be necessary to explore digitalization to stay relevant.

4. Cost-Benefit Analysis: Conduct a thorough cost-benefit analysis to determine if the potential benefits of digitalization outweigh the costs. If the investment doesn't offer a reasonable return, it might not be justified.

5. Resource Availability: Evaluate whether you have the necessary resources, including financial resources, technical expertise, and staff training, to implement and sustain digital solutions effectively.

6. Future Growth: Consider the scalability of your organization. Even if you don't currently see a clear use case for digitalization, it's essential to think about your organization's future growth and whether digital technologies could play a role in that growth.

7. Technology Trends: Stay informed about industry trends and emerging technologies. While there may not be an immediate use case, technological advancements could create new opportunities down the line.

8. Customer Feedback: Engage with your customers or stakeholders to gather feedback on their needs and preferences. They may provide insights that could uncover potential use cases for digitalization.

9. Pilot Projects: Instead of a full-scale digital transformation, consider starting with smaller pilot projects to test the waters and assess the feasibility and impact of digital solutions in a controlled environment.

10. Consult Experts: Seek advice from digital transformation consultants or experts in your industry. They can provide insights into potential use cases and help you determine if digitalization is appropriate for your organization.

In some cases, it may indeed be the case that digitalization doesn't make sense for your organization at a given time. However, it's essential to regularly revisit this assessment as technology and business landscapes evolve. What might not be relevant today could become essential in the future. Ultimately, the decision to pursue digitalization should be guided by a thorough understanding of your organization's unique needs and circumstances."

- https://chat.openai.com (Does it make sense to think about digitalization if we don't see any use case?)

Often the person who knows the answer or the right way is closer than you think. All you have to do is ask.

If you choose the path to the left at the crossroads, you will not be able to pick the fruit that grows on the path to the right.
So collect all the requirements and decide which ones you want to choose and which ones you want to eliminate by weighing up the pros and cons.

I have found the solution !!!
But unfortunately the problem did not match my solution.
:-)