**Document directory**
- Problem domain analysis
- Product Problems

*"You don't overcome challenges by making them smaller but by making yourself bigger ."*-John C. Maxwell

*You cannot overcome the challenge by reducing it, but you should overcome it by making yourself bigger.*

** **

Every one of us has problems. Problems are part of our lives and they will always come out. Instead of avoiding problems, I prefer to embrace the problem and actively respond to it instead of escaping. Based on this, the most effective thing is to learn the technology to solve the problem and become a problem solver. I talked about the problem for the first time in my personal management: the solution to the problem is a re-emergence of an exercise that uses it as an agile result.

**Your results****:** Learn how to solve problems systematically and become a skillful problem solver.

In**30-day agile results: Opening**As mentioned in the following section, we will conduct agile results exercises. The previous article 25: fixed time, flexible range learning, using time boxes for energy management. Today we will conduct the 26th day of getting result exercises: solve the problem (day 26-solve problems with skill ).

**Step 5 solve the problem**
**Use "how" to describe the problem**

A target-based problem is an effective method for describing the problem, for example, "How to get more friends and influence them", "How to Write faster", "How to solve problems xyz", or "how to motivate yourself ". A brief description of the problem can force us to clarify the problem, make it easier to execute the problem, find the existing solution, and share your problem with others to quickly obtain support.
**Find possible solutions**

There are few problems that we encountered first. When encountering problems, we should find out who has encountered the same problem as you and who has solved the problem. Finding three possible solutions forces you to broaden your horizons and look for possibilities. You can see how people you know or do not know solve such problems. It is much better to learn from them to solve the problems than to start from scratch.
**Test your results**

The problem will not automatically disappear. You can only take action and test your results. After the action, you must be successful or get feedback. The worst case is that you find something amazing, but it also shows that your goal is getting closer and closer.
**Change your Method**

If the test does not work, you may need to change your method.**Einstein believes that it is an abnormal mental performance to expect to repeat one thing repeatedly to get different results.**If you don't know how to change the method, start self-conversation and ask yourself some better questions. If the problem persists, ask other people and you will find that you can always find someone who will provide you with suggestions. Because everyone has different expertise, if you get advice, you need to make sure that you ask the right person and ask the right questions.
**Refining Problems**

We often find that we have always understood superficial aspects at the beginning of the problem, but our understanding of the problem is more mature with multiple exercises and real feedback.**How to define and refine the problem can help us get closer to the solution.**

**Good at solving problems**
- You can clearly define problems and focus on potential fundamental problems.
- You find that you can easily reframe problems to motivate yourself.
- You find that you can easily discover more possibilities, rather than locking in a solution.
- You will immediately test your solution, instead of postponing it to a later stage.
- You have a faster and simpler way to get feedback
- You have built a network to help you better solve problems.

**Why not be good at solving problems?**
**Wrong question**
**Blame others**
**Always in an inefficient state**
**I did not ask others to help myself**
**No proper tool**
**Only thoughts, no actions**
**Do not speak**

**Slang related to problem solving**
The following are some sayings about how to solve the problem. If there are too many sayings, we will not translate them one by one:

- "A problem well stated is a problem half solved."-John Dewey
- "Don't dwell on what went wrong. Instead, focus on what to do next. Spend your energies on moving forward toward finding the answer."-Denis waitley
- "Focus 90% of your time on solutions and only 10% of your time on problems."-Anthony J. d' Angelo
- "For every problem there is a solution which is simple, clean and wrong."-Henry Louis Mencken
- "Have you got a problem? Do what you can where you are with what you 've got. "-Theodore Roosevelt
- "How you think about a problem is more important than the problem itself-so always think positively."-Norman Vincent Peale
- "In times like these it is good to remember that there have always been times like these."-Paul Harvey
- "It is not stress that kills us. It is valid adaptation to stress that allows us to live."-George Vaillant
- "It's not that I'm so smart, it's just that I stay with problems longer."-Albert Einstein
- "Laugh at your problems; everybody else does."-Anonymous
- "Leaders are problem solvers by talent and temperament, and by choice."-Harlan Cleveland
- "Man is the only animal for whom his own existence is a problem which he has to solve"-Erich Fromm
- "Most people spend more time and energy going around problems than in trying to solve them."-Henry Ford
- "Never try to solve all the problems at once-make them line up for you one-by-one."-Richard sloma
- "No problem can stand the assault of sustained thinking."-Voltaire
- "Problems are to the mind what exercise is to the muscles, they toughen and make strong."-Norman Vincent Peale
- "Some problems are so complex that you have to be highly intelligent and well-informed just to be undecided about them."-Laurence J. Peter
- "Stop looking for solutions to problems and start looking for the right path."-Andy Stanley
- "The measure of success is not whether you have a tough problem to deal with, but whether it is the same problem you had last year."-John Foster Dulles
- "The problem is not that there are problems. The problem is expecting otherwise and thinking that having problems is a problem."-Theodore Rubin
- "The way we see the problem is the problem."-Stephen Covey
- "Uncertainty can lead to paralysis. And if you become indecisive you're dead .."-Jim Citrin
- "We can't solve problems by using the same kind of thinking we used when we created them."-Albert Stein
- "When you come to a roadblock, take a detour."-Mary Kay Ash
- "Worry is like a rocking chair-it gives you something to do but won't get you anywhere."-Anonymous
- "You won't find a solution by saying there is no problem."-William rotsler

**What I want to do today**
- Find a problem you want to solve and write it in the "how..." way (for example, how to make my blog have 10000 subscribers)
- Find three people or solutions you can imitate
- Test a solution and get feedback at the same time. Use feedback to help you improve the solution or change your method.

Refer:

**Problem solving techniques**

Personal Management: how to deal with problems

When we encounter problems, that is, when we leave the comfort zone, we will feel uncomfortable at first, or feel a lot of pressure, or even a crash. At this time, we need to adjust our views on the problem and learn how to solve the problem. This article will share with you some content related to solving the problem.

Excellent people are good at solving problems. Only by facing problems bravely can we discover our potential and awaken our ability to solve problems. The best way to face the problem is to be responsible for the problem, face the problem bravely, and use your brains to solve the problem.

Problem domain analysis

**Is it a common issue or a personality issue?**

Question

The first step in question analysis is to determine whether the problem we encounter is a common problem or a personality problem. Many of the problems we encounter are actually problems that have already been encountered by others. At this time, we can stand on the shoulders of others to quickly design solutions and solve them.

Determine it. For example, the design pattern in development is a series of application design solutions that guide the development from the design problems encountered in software design. If it is a brand new problem, it is more difficult than a common problem, but more challenging.

Combat, we can also introduce some tools and methods in different specialties to gradually develop solutions. If there is no definite result, you can use assumptions and quick verification to find a solution to the problem.
**What is the best source of information?**

Understanding the problem and proposing a solution require a lot of information support. Finding some good information sources can save your time, we can find useful information through colleagues, friends, blogs, websites, forums, and so on to help with decision-making and execution. When collecting and learning information, we need to know what we know, what we don't know, and what we need to know next?
**What is hot spots?**

Through information collection and understanding of problems, we can better group problems and tasks to different hot spots after setting the problem. Through hot spots, we can better collect, organize and extract more useful information. For example, the popularity of agile individuals is as follows:

**What are the main problems?**

Pair

After the problem is stated, we need to ask a few more "why" to find the root problem behind the appearance. This is what we must do when analyzing user requirements in product development. After confirming the problem, it is possible for me

At the same time, we need to solve multiple problems. Even a problem, the root problem will spread out more detailed problems. At this time, we need to prioritize the problems solved according to the current context, find out the main problems. Only find

You can solve the main problem faster and more accurately.
**What are possible solutions?**

If the problem already exists, the first thing we should do is to analyze how this problem was previously solved. In this case, we should not only limit our experience. We can check whether other people have solved the problem or whether there are solutions to similar problems in other fields.

The existing solutions do not necessarily solve our problems, because they are all developed based on a certain context. At this time, we need to find the "why" and "when" behind the solution to analyze whether it is the same as the current environment.
**What resources can be coordinated to better solve these problems?**

When you have sufficient information about the problem and solution, you may find that you are not the most suitable person to solve the problem. You cannot effectively solve these problems by yourself, at this time, we need to find and coordinate external resources to solve it.
**What are the test results?**

After the problems, solutions, and resources are identified, we will immediately test and verify different solutions. In this case, we may need to constantly adjust the solutions under monitoring, finally, make a decision and solve the problem well.

Product Problems

When building the product architecture, our primary concern is not detail functions, but whether we can grasp the core needs of users and whether the value propositions provided can bring real benefits to users.

**Different levels of problems**

During product architecture, we often discuss topics at different layers or with different granularities, or discuss business issues and technical issues at the same time, the reason for this is that we do not have a clear understanding of the problem.

For different problem areas, there are two areas: one is the problem area and the other is the solution area. The product problem pyramid below can better express the problem level.

For**Market-driven products**For example, if the customer needs to drive user needs, formulating a solution after the problem is fixed will lead to product problems and technical problems. Business problems and technical problems are interrelated, as shown in. Each business problem can be solved by a business solution, which brings new business and technical problems:

**Discover problems and express them through models**

After understanding the levels and associations between problems, we can continuously analyze the problems through simple "why" and "what" methods until we find the appropriate granularity.

In addition**Problem solving techniques**There are more problem solving technologies. If you are interested, you can study and practice them together.

** **

0: Start

1: overall understanding of the agile getting result Method

2: drive your week with three stories

3: drive your day with three stories

4: give up some things

5: Use a heat map to identify important events

6: Review on Friday and find three things that need to be improved.

7. Set the Boundary Value and buffer.

8: Clear the brain and release pressure

9: You must, should, and can determine the priority of daily events.

10: give full play to your advantages

11: High Performance and slow life

12: Efficiency role-are you the starter or the completer?

13: how to put things into action

14: Important

15: Put yourself in peace

16: use metaphor to motivate yourself

17: find efficient time and use it to handle important things

18: Increase the creative time for every week

19: Who are you working?

20: Good questions can produce good results.

21: Positive failures, lessons learned, and improvement results

22: design your day

23: design your week

24: restore your energy

25: fixed time, flexible range

**Recommended: online e-books you may need**

**Agile individual Sina apron: http://q.t.sina.com.cn/135484**

**You are welcome to reprint it. Please note: It is reprinted from agile personal websites.**