Measure It

Have you encountered a problem that is taking too long to respond? Not even close to a solution.

You may want a quick solution in less than one hour, but unfortunately, it is 10 miles away from your current standing for hope.

The rule of thumb for a solution is a deep dig into the real problem, understanding clearly, asking probing questions, and validating your perspective. Asking the right question will act as a bridge between your knowledge and the problem itself.

When you realize the same problem is occurring again and have no clue how this could happen again. In this stage, you must learn, "You can't control what you can't measure." Yes, it is a valid statement. If you can't reach something, How would you touch and manage it properly? You need data that explains what really happened at that time.

Once you understand the problem clearly, find a cross line, analyze the pattern, and validate your theory, backed with previous experience and brainstorming sessions. You start drawing upon the solution by gradually interpreting it as a chunk solution, as it will build up a comprehensive antidote.

When designing something, put a proper tool in place, get important data as much as possible to catch, analyze the trends, and adjust accordingly. In software, you need to set logs properly that can tell when (timestamp), what (error line), who (devices/actor), and why (trace log). Finding How after you understand the 4 W's is much easier.

Measuring something should be dynamic in terms of challenging your requirement to achieve a shared objective in the future. Obviously, change always happens all the time. You can't rely on tools or solutions for five years; they must allow for growth and remain relevant.