How to problem-solve

Do you want to idea-develop?

First data-collect and data-mine. As you evidence-gather, pattern-match and trend-spot. Deal-make and cost-cut as you assumption-test, then course-correct. Don’t context-switch until you assumption-test. When you friction-reduce and bottleneck-remove, you can priority-set and resource-allocate. If you’re ambitious, you might even change-manage.

Before you signal-boost, make sure you bug-fix and fact-check. Demand-forecast. Quality-assure, story-frame, and message-test first, then relationship-build and knowledge-share.

Take a moment to insight-generate and lesson-learn. You’ll profit-maximize.

Loop-close. Case-close. Habit-reinforce.

And prepare to problem-solve again.

Think before hyphenating verbs

Real people develop ideas, collect data, correct their course, fix bugs, check facts, correct errors, assure quality, and test messages. They build relationships, share knowledge, reinforce habits and close loops.

Text is easier to understand when transitive verbs have objects.

That’s how good writers problem-solve. Er, I mean, solve problems. Sorry, just needed to error-correct.