Most people treat problem-solving like it's one skill among many — alongside communication, leadership, technical know-how. They list it on résumés. They nod when someone mentions it.
That framing is wrong. Problem-solving is the meta-skill. It's the operating system that everything else runs on. Leadership is just applied problem-solving. Strategy is just structured problem-solving. Execution is just sustained problem-solving under pressure.
Every person, team, company, and civilization that has ever moved forward did so because someone — somewhere — refused to accept that the obstacle was permanent. They figured it out. That is FIGUREOUTABILITY.
There are two dangerous assumptions that kill figureoutability before it even starts:
"Someone else will solve this."
This assumption transfers the problem without solving it. It creates dependency, fragility, and eventually irrelevance. When you outsource your problems habitually, you outsource your agency with them.
"This problem can't be solved."
Every unsolvable problem that was later solved looked impossible until it wasn't. Penicillin. The polio vaccine. The iPhone. Commercial steel. Every one had moments where serious, smart people said it couldn't be done. Someone with figureoutability disagreed.
In the early days of Boeing's commercial aviation push, a design problem had stalled the engineering team for weeks. A janitor cleaning the conference room heard the engineers arguing and quietly said, "Couldn't you just angle the landing gear inward?" He'd seen similar geometry on a cart he repaired in the warehouse.
That observation — from someone with zero aeronautics training and 100% figureoutability — became a core structural feature of the plane. He saw a problem. He didn't assume his rank disqualified him. He spoke up.
Figureoutability doesn't respect credentials. It respects engagement.
Here's the uncomfortable truth: figureoutability is only proven under pressure. Anyone can problem-solve when stakes are low, time is generous, and resources are flush. The real test is:
"You cannot teach leadership, resilience, innovation, or grit in isolation. All of them are downstream of one thing: the willingness to face a problem and refuse to leave it unsolved."
The Foundation of FigureoutabilityEvery person on a team — and every voice in your own head — responds to problems from one of three positions. Learning to identify them accurately is one of the highest-leverage leadership skills there is.
| Dimension | Figureoutability | Complainer | Entitlement |
|---|---|---|---|
| Sees a problem and… | Moves toward it | Voices it loudly | Pretends it's yours |
| Wants change? | Yes — and acts | Yes — but won't act | No — unless it benefits them |
| Wants to work? | Yes | No | Absolutely not |
| Can be developed? | Already there | Yes — high potential | Extremely rare |
| Energy type | Forward force | Blocked energy | Drain / vacuum |
| Leadership move | Empower & trust | Channel & assign | Remove or contain |
Most leaders write off complainers. That's a waste. A complainer is someone who cares enough about a problem to notice it and say something. That's actually a positive signal buried under frustrating packaging.
The complainer's problem isn't awareness — it's activation. They see the gap between what is and what should be. They feel it. They talk about it. What they haven't done is claim ownership of closing that gap.
Give them the problem. Literally. Not "that's a great point, I'll look into it." Say: "You're right — that's a real issue. I want you to own solving it. Here's your deadline and your authority. What do you need from me?"
What happens next tells you everything. If they light up: future leader. If they backpedal and suddenly the problem isn't so bad: closer to entitlement.
A warehouse manager had an employee who complained constantly about the receiving process being slow. Every Monday meeting, the same theme. The manager finally said: "You've identified a real problem. Starting today, you own the receiving process. Redesign it. I'll back your decisions."
The employee paused, then got quiet. The following week he came in with a two-page workflow redesign. Within a month, receiving time dropped 40%.
He wasn't a complainer by nature. He was a leader who hadn't been given a door to walk through.
Entitlement is not a personality flaw — it's a posture toward reality. The entitled person believes the world owes them resolution. They expect effort to flow toward them rather than from them.
The complainer lacks activation. Give them responsibility and they often rise. The entitled person lacks the belief that they should have to rise. No amount of encouragement, systems, or incentives will change someone who fundamentally believes the problem is everyone else's job.
Entitlement isn't a gap in skill. It's a gap in philosophy. And philosophy changes slowly, if ever, unless the person chooses it.
Before you apply this lens to your team, apply it to yourself. Think of the last significant problem you faced. Write one sentence describing how you responded in the first 24 hours. Does that sentence reflect figureoutability, complaint, or entitlement?
The honest answer tells you more than any assessment ever could.
"When the angel of the Lord appeared to Gideon, he said, 'The Lord is with you, mighty warrior.' 'Pardon me, my Lord,' Gideon replied, 'but if the Lord is with us, why has all this happened to us? Where are all his wonders that our ancestors told us about when they said, Did not the Lord bring us up out of Egypt? But now the Lord has abandoned us and given us into the hand of Midian.' The Lord turned to him and said, GO IN THE STRENGTH YOU HAVE AND SAVE Israel out of Midian's hand. Am I not sending you?"
— Judges 6:12–14 NIVGideon's complaint, stripped of emotion, was actually precise: Our people are enslaved. Our history says we should be free. These two facts don't reconcile. That's not whining — that's a legitimate problem statement. He identified the gap between current state and intended state with clarity.
Gideon assumed the problem required external intervention before it could be addressed. He was looking backward at miracles God had performed rather than forward at the one he was positioned to lead. His assumption: "I cannot move until conditions change." God's reframe: "Conditions will change because you move."
Gideon had legitimate constraints. He was the weakest member of the weakest clan. No army, no plan, no track record. These weren't excuses — they were real. And they didn't change the assignment. Constraints define the parameters of figureoutability, not its impossibility.
God didn't argue with Gideon's complaint. He didn't dismiss it, fix it from above, or list reasons it wasn't so bad. He did exactly one thing: He handed Gideon the problem as an assignment.
"Go in the strength you have." Not the strength you wish you had. Not the strength you'll have later. The strength available right now is enough to start.
A regional manager had a coordinator who complained for months about chaotic delivery scheduling — lost orders, wrong materials, delays. Instead of defending the system, the manager said: "I agree. You know this better than anyone. Build me a better one. You have 30 days and my full backing."
The coordinator built a tracking system that later became the company standard. Two years later she was running logistics for the entire division.
The complaint was the résumé. The assignment revealed the leader.
"Go in the strength you have" — is the original definition of figureoutability. You don't need more before you start. You need to start with what you have.
Judges 6:14 · The Gideon PrincipleFigureoutability is not random. High performers follow a logic, often without knowing it. This framework makes that logic explicit so you can teach it, apply it under pressure, and train your team to use it.
Write the problem in one sentence. If you can't, you don't understand it yet. "We have communication problems" is not a problem. "Field crews don't receive updated specs before arriving on site" is.
List what you're taking for granted. Most failed solutions fail because they solve the assumed problem, not the actual one. What would change your understanding if it turned out to be untrue?
What can't you change? Budget, time, people, regulations. Now list the unknowns — things you don't know that matter. Constraints define the playing field. Unknowns tell you where to investigate first.
Complex problems feel unsolvable because they're bundled. Unbundle them. A failing project is usually five separate problems — scheduling, scope creep, communication, resourcing, and accountability.
Force yourself to identify three genuinely different solutions — not variations of the same idea. One conservative, one moderate, one bold or unconventional. This prevents anchoring on the first idea.
Speed vs. quality. Cost vs. control. Short-term vs. long-term. Write out the tradeoffs honestly. The right answer is rarely obvious until you've named what each option actually sacrifices.
Make a decision. This step kills more would-be leaders than any other. Analysis paralysis is just fear wearing a lab coat. Given what you know now — choose. You can adjust as you learn more.
A plan without a sequence is a wish. Write the steps. Assign who does what by when. Good execution is boring and specific on purpose — vague plans create vague results.
Before you execute, ask: where is this plan most likely to break? Anticipate 2–3 places where things go wrong. Build a contingency for each. This isn't pessimism — it's professional preparation.
The first solution is rarely the final solution. Build in a review point. What did you learn? What would you do differently? Execute → learn → improve is how figureoutability compounds over time.
Problem (Step 1): A steel building kit is delayed 6 weeks by the manufacturer, but the customer's foundation contractor finishes in 10 days.
Assumptions (Step 2): Assumed the manufacturer would hit original lead time. Assumed no buffer in customer's schedule. Assumed no alternative suppliers.
Constraints (Step 3): Contract penalties for delay. Foundation crew has a hard end date. No budget margin for premium shipping.
Sub-problems (Step 4): Customer communication. Alternative sourcing. Foundation scheduling. Contract review. Cash flow for potential penalty.
3 Approaches (Step 5): A — wait and absorb penalties. B — source competing supplier at premium. C — offer customer a scope upgrade in exchange for goodwill on the delay.
Chosen (Step 7): Option C, with B as fallback. Call customer same day.
Result: Customer accepted the delay in exchange for a building upgrade. Relationship strengthened. Zero penalties. The problem became a sales moment.
Post these 10 steps where your team can see them. When someone brings you a problem, ask: "Which step are you on?"
This trains the habit of working the problem first rather than escalating it. Over time, that one question alone changes the culture.
Businesses don't fail because of bad markets. They fail because problems accumulate faster than they get solved. Every operational bottleneck is a solved problem waiting for someone to care enough to engage it.
A small contractor was losing jobs to competitors who could turn quotes faster. He assumed it was a pricing problem. When he applied the framework, he found the real issue: he was the only one who could build a quote. No template, no delegated authority, no system.
He built a basic estimating template, trained one person to handle standard jobs, and cut quote turnaround from 5 days to same-day on 70% of jobs. Revenue climbed 28% in one quarter — not because costs changed, but because a problem got solved instead of tolerated.
The leader who models figureoutability creates a permission structure that changes the whole team. When people see you face hard problems without blaming, without folding — they believe it's possible for them too.
You cannot teach what you don't demonstrate. If you want a team with figureoutability, they need to watch you hit a wall and figure out how to get through it — not because you're invincible, but because you refuse to stop.
Your ceiling becomes their floor.
The most important application of figureoutability is personal — when the problem isn't a process but your own life circumstances. Job loss, health crisis, financial collapse, relational breakdown. These aren't times when the framework feels natural. They're times when it's most essential.
A business owner lost his primary revenue stream when his largest client — 60% of revenue — terminated their contract without warning. He treated it like a business problem rather than a catastrophe. Step 1: defined it specifically: "I have a 6-month runway before cash runs out." Step 4: identified sub-problems — pipeline, cost structure, pivot options.
Within four months he had rebuilt revenue through a different customer segment that was more profitable and more stable than the one he'd lost. The crisis restructured the business for the better.
Adversity doesn't build figureoutability. It reveals it. But you can build it before the test comes.
Every business innovation started as someone refusing to accept a problem as permanent. The opposite of figureoutability isn't just complaint — it's also resignation. "That's just how it works" is the death sentence of innovation.
Most relationship breakdowns happen not from the size of the conflict but from the absence of figureoutability applied to it. People choose to stay stuck in complaint instead of owning the change they want to see.
The next time you're frustrated with someone, apply Step 1: define the core problem in one sentence. Not "they're difficult." Not "communication is bad." Try: "When I give project updates in group meetings, they interrupt before I finish and the team gets confused about priorities."
Most relationship conflicts dissolve or shrink significantly the moment you actually define them.
You can model figureoutability personally and still lead a team that defaults to complaint and dependency. Culture doesn't change just because the leader changes — it changes when the systems, stories, expectations, and consequences all align to reinforce a different way of operating.
Culture = What you celebrate + What you tolerate + What you model
If you celebrate figureoutability but tolerate chronic complaint and model avoidance — you don't have a figureoutability culture. You have a gap between stated values and lived reality. People see that gap and file it under "this place isn't serious."
When someone brings you a problem, your default response determines the culture. Wrong response: solve it for them. Right response: "What have you tried so far?" or "What do you think the options are?" This doesn't mean you don't help — it means you require engagement before you add yours.
If people only get recognized when their solution works, they'll stop trying unproven solutions. Celebrate the person who tried something bold, documented what they learned, and reported back honestly — even when it didn't work. That person is more valuable than the one who plays it safe and never fails.
Every significant recurring problem in your business should have a named owner — one person accountable for the state of that problem at any given time. Not a committee. Not "the team." One name.
That person doesn't have to solve it alone, but they have to know the current status, be actively working it, and report progress. Problems without owners become permanent.
Organizations operate on narrative. The stories people repeat define what they believe is possible and what is valued. Collect and tell figureoutability stories from your own team. The person who redesigned the process. The one who solved the supplier problem at 6pm Friday. The crew member who improvised a fix on-site that saved the job. These stories do more to build culture than any policy document.
One chronically entitled person costs you more than their salary. They signal to everyone around them: you can opt out of responsibility here and still stay. Your top performers — the people with the most options — will either leave or lower their standards.
The absence of consequences for entitlement is a message. Make sure it's the message you intend to send.
Moving too fast. Culture changes in months and years, not days. Announcing "we're now a figureoutability culture" and expecting immediate behavior change creates cynicism. Show it before you say it.
Applying the standard selectively. If leadership is exempt from the expectation, the whole framework collapses. Leaders have to go first, go hardest, and be the most honest about what they're still learning.
Punishing failure too quickly. Figureoutability requires experimentation. Experimentation produces failure. The question is never "did it fail?" — it's "did they learn and adjust?"
Not celebrating loudly enough. Figureoutability wins get a quiet nod while complaints get loud attention. Reverse this. Make recognition visible and specific.
List every significant problem you are currently tolerating — in your business, team, processes, finances, and relationships. Don't filter. Don't explain. Just list them. Then next to each one, write one of three labels:
Count the Complaining and Waiting items. That number is your figureoutability gap. It's not a judgment — it's a starting point.
Choose one problem from your inventory — ideally the one you've been tolerating longest. Run it through all 10 steps. Write it out. Don't skip steps. The act of writing forces clarity that thinking alone rarely produces.
Identify one person on your team or in your circle who is a consistent complainer about a specific issue. Apply the Gideon Principle. Give them the problem as an assignment with real authority and a real deadline. Document what happens. Whether they rise or retreat, you'll have learned something essential.
This course is version one. After you've taught it and watched it work or fail in your context, come back and improve it. Good systems are never finished.
"Go in the strength you have."
— Judges 6:14 NIV · The Original Definition of FigureoutabilityYou don't need a perfect system to start. You don't need perfect conditions or perfect confidence. You need the willingness to face what's in front of you and refuse to leave it unsolved.
That is Figureoutability. That is leadership. That is everything.