What is ProblemOps?
ProblemOps is a system of communication tools that teams can use to build a shared understanding while making change. It combines skills and methods from UX, product management, operations, and strategy. Read the introduction to the discipline here: Introducing ProblemOps.
What Does ProblemOps Stand For?
ProblemOps stands for "Problem-Solving Operations". Breaking it down: Problem-solving is making change in the world, and Operations is the practice of carrying out work. ProblemOps teaches us how to work together to make change.
Why should I care?
If you make change for a living (in UX, or business, or product management, or something else), you've probably struggled with getting on the same page or generating buy-in. This system can help you do that across teams, and quickly. Without working together and understanding each other, we won't change anything.
Who made ProblemOps?
Morgan Denner created the system of ProblemOps from the 12 years of many different kinds of work. Check out more the About Us page.
What's the difference between ProblemOps and UX?
User experience professionals solve problems for a living (and a whole lot more). ProblemOps provides ways for them to build shared understanding and collaborate across functions.
What's the difference between ProblemOps and Product Management?
Product professionals orchestrate and drive change. ProblemOps helps you develop a language around the change you propose, plan, and deliver. Get everyone aligned and moving toward the same outcomes with ProblemOps.