HELPING COMPANIES
TEST, VALIDATE
& LAUNCH.

Sprint teams. Real outcomes.

We map opportunities, design concepts, and hand over working capability, on demand, without the overhead of building an innovation function from scratch.

→ View ServicesGet in touch
WHOS
WHO.
What we do
ONE TEAM.
FOUR MODES.

One standard: something ships. A cross-functional team embedded inside your problem, no stake in your politics, no overhead to justify. Weeks, not quarters.

01 MAP
Opportunity Mapping
Structured engagements that identify, evaluate, and prioritise opportunities. We hand you a clear brief for what to build next.
Discover Validate Prioritise
Start →
02 DESIGN
Concept Design
Transforming opportunities into executable initiatives, products, or ventures. A tested prototype and a real signal before you commit the budget.
Prototype Test Validate
Start →
03 HANDOVER
Handover & Scale
Transitioning ownership with playbooks, training, and systems so the capability stays when we leave. We leave you better than we found you.
Playbook Train Scale
Start →
ONGOING
Innovation Advisory
Embedded strategic support for leadership teams navigating growth, transformation, and innovation. Not a report, a retained presence.
Retained Roadmap Advisory
Explore →
What we work on
PROBLEMS WE SOLVE.
AND WHO WE SOLVE THEM FOR.

The common thread is never the industry — it's the moment. The one said in the meeting before anyone makes the call.

Discover
"We know something needs to change. We don't know where to focus."
Design
"We have a direction. We need a real signal before we commit the budget."
Scale
"It's working. We need the knowledge locked in, the team trained, and the system able to run without us."
Advise
"We need ongoing support, not another one-off project that ends with a slide deck."
Who we solve it for
Corporates Family Businesses Government Entities Startups SMEs Scale-ups
→ Start Your Brief
Next steps
LET'S TALK
IT THROUGH.

Not ready for the full brief yet? Leave your details and we'll reach out to set up a short intro call — to understand where you are and point you to the right next step.

A 30-minute call with an advisor, not a sales pitch.
We'll help you scope the right sprint for your situation.
Confidentiality is a default, not an option.
Intro call
Tell us how to reach you
What's on your mind?
Where you are
Finding the right opportunity Testing a concept Ongoing innovation support Handover & scale AI implementation Not sure yet
Timeline
This quarter Next quarter Just exploring
No commitment — just a conversation. We'll reach out within 24 hours.
How we work with you
THREE WAYS
TO ENGAGE.

From a few days to a few months — pick the depth your moment calls for. Every one of them ends in something real.

01 · Days
Innovation Workshops
Facilitated sprints and ideation inside your team — alignment plus real capability.
1–5 days · per workshop
Explore →
02 · Weeks
Innovation Sprints
An embedded team maps, designs, tests, and hands over a real outcome — in weeks.
4–8 weeks · fixed fee
Explore →
03 · Months
Entrepreneur in Residence
Borrow a seasoned builder-operator, embedded to lead a 0→1 venture or run your program.
3–12 months · retainer
Explore →
← All services
Offering 01 · Days

INNOVATION
WORKSHOPS.

Facilitated, hands-on sessions delivered inside your team — design sprints, opportunity framing, ideation and prioritisation — that create alignment and a real output, while building your team's innovation muscle.

Ideal for
  • Corporate innovation and transformation teams
  • Leadership offsites that need alignment or a decision
  • Learning-and-development programs building capability
What you get
  • A facilitated session with a defined output — a prioritised backlog, a tested concept, a decision made
  • The methods and templates your team keeps and reuses
Format

Half-day to five days. A single workshop or a running program. On-site or remote.

→ Book a workshop In the spirit of IDEO U, LUMA, and Board of Innovation — built for your context.
← All services
Offering 02 · Weeks

INNOVATION SPRINTS.

Fixed-scope, time-boxed sprints. An embedded cross-functional team works inside one problem and hands over a real output. Pick the mode that fits your moment.

WHAT DO YOU NEED?
01
Map
02
Design
03
Scale
ONGOING
Advise
01Map
02Design
03Scale
ONGAdvise
Ongoing
Advise
INNOVATION ADVISORY

Embedded strategic support for leadership teams navigating growth, transformation, and innovation. Not a report. A retained presence that keeps the organisation moving, mapping what to build, guiding how to build it, and keeping the right bets in motion.

Format
Retained engagement
Timeline
Starts within 2 weeks
What you get
Innovation roadmap + ongoing sprint cadenceMonthly strategy sessions with leadershipRolling 90-day roadmap · sprint facilitation · decision support
Includes: Strategic Direction · Decision Support · Organisational Clarity · Accountability
01Map
02Design
03Scale
ONGAdvise
Stage 01
Map
OPPORTUNITY MAPPING

You know something needs to change but you don't know where to focus. We map the landscape, validate the right opportunity, and hand you a clear brief for what to build next, so you're not six months into the wrong thing.

Format
4-week sprint
Timeline
Team assembled within 72h
Deliverables
Opportunity Brief + Product BriefLandscape analysis · prioritised opportunities · recommended focus areaConcept direction · success metrics · build-ready brief
Best for: Organisations that have been circling the same problem without a clear starting point, and need someone outside the politics to map it.
01Map
02Design
03Scale
ONGAdvise
Stage 02
Design
CONCEPT DESIGN

You have a direction. You need a tested prototype and a real signal before you commit the budget. We design the concept, build a prototype, and run it past real users, so you know if you're solving the right problem before you build the wrong product.

Format
4–6 week sprint
Timeline
Team assembled within 72h
Deliverables
Tested prototype + validation reportFunctional, user-tested concept · real signal before you commitGo / no-go recommendation with rationale
Best for: Teams with a direction and a hypothesis, who need a real signal from real users before committing budget to the build.
01Map
02Design
03Scale
ONGAdvise
Stage 03
Scale
HANDOVER & SCALE

The work is done. Now we make sure it stays done. We transition ownership with playbooks, training, and the systems your team needs to scale independently, so the capability we built together doesn't walk out the door when we do.

Format
Final phase of engagement
Timeline
3–4 weeks
Deliverables
Operations playbook + team handoverProcesses, tools, and decision frameworks documentedLive training sessions · 30-day post-handover support
Best for: Organisations who want the capability embedded, not just borrowed. What we build together stays with you.
Strategic Clarity · Sprint

Sprint types & typical timelines
01. Map
4 weeks
Opportunity Mapping, identify, evaluate, and prioritise opportunities. Delivers a 15–20 page Opportunity Brief + Product Brief.
02. Design
4–6 weeks
Concept Design, transform an opportunity into an executable initiative. Tested prototype and real user signal before you commit budget.
03. Scale
3–4 weeks
Handover & Scale, playbooks, training, and systems to transition ownership so your team can scale independently. We leave when the team can run it without us.
Ongoing. Advise
Retained · Monthly
Innovation Advisory, embedded strategic support for leadership teams navigating growth, transformation, and innovation.
→ Start a Sprint The relationship without the retainer. Until you want one.
← All services
Offering 03 · Months

ENTREPRENEUR
IN RESIDENCE.

Borrow a seasoned builder-operator — someone who has built before — embedded inside your company or accelerator to lead a 0→1 venture, shape strategy, or run a program, with skin in the game for a defined period.

For companies

An experienced founder-operator to lead a new venture or product line from the inside — when you don't have that person on the team yet.

For accelerators & funds

An EIR to source and evaluate opportunities, mentor cohorts, and lead programs — an operator who has actually built, not just advised.

Format

Part- or full-time embed, 3–12 months. Retainer, with upside where it makes sense.

→ Talk about an EIR In the spirit of Antler, Entrepreneur First, and Flagship — for this region.
WHOS
WHO.
Home Services Get in touch About Falsafa
✕ Exit
Step 1 of 4
WHAT TYPE OF ORGANISATION ARE YOU?
Helps us scope the right sprint and assemble the right team for your specific context.
Startup / Early-stage
SME (50–500 people)
Corporate / Enterprise
Government / Public sector
Family business
Opportunity Mapping Sprint
BRIEF RECEIVED.

Execution starts here. We'll be in touch within 24 hours.

What happens next
1
Our team reads your brief within 24 hours and scopes the right sprint for your challenge.
2
We assemble the cross-functional team best matched to your specific problem.
3
We kick off. You'll have something real, validated, designed, or built, within the sprint window.
Want to talk first?
Book a free 20-min discovery call. No commitment.
[Calendar embed. Calendly / Cal.com]
Enterprise & Teams
LET'S DESIGN YOUR PROGRAMME.
Tell us about your team and what you're trying to achieve. We'll come back to you within 24 hours with a tailored structure and pricing.
Company / Organisation
Your role
How many people are you enrolling?
What are you trying to achieve for your team?
Sprint type interest
Indicative budget
We'll come back to you within 24 hours. No sales calls unless you want one.
Enterprise Request Received
WE'LL BE IN TOUCH.

Someone from our team will reach out within 24 hours to design your programme.

What happens next
1
We review your team's goals and structure a tailored sprint programme, sprint type, cadence, and advisor matching.
2
We send you a programme overview and pricing within 24 hours. No generic decks, built for your team's specific goals.
3
You confirm, we onboard your team, and sprints begin on your timeline.
Project Portal
CREATE YOUR ACCESS
Your brief is ready. Create a secure account to meet your matched advisor, sign your NDA, and follow the sprint. No password, we email you a one-time code.
Enter your name and a valid email.
🔒 Confidential by default. Your identity is never shown to an advisor until you choose to proceed.
Dashboard
OnboardingSprint starts in 3 days

WELCOME, NOUR.

Your Strategic Clarity sprint begins May 9th.

Strategic Clarity Sprint
Sprint #004 · 4 weeks
Your Advisor
Matched to your brief
🧠
Advisor A
Go-to-market · SaaS
Matched because you're navigating a positioning challenge ahead of a raise, exactly where this advisor's expertise sits.
Schedule intro call →
Your Sprint
Starting May 9
1
Define
2
Run
3
Decide
Next: Define session · May 9, 10:00 AM GST
Pre-Sprint Checklist
1 of 3 done
Upcoming Sessions
View all
Dashboard
● Sprint ActiveWeek 2 of 3
Strategic Clarity · Sprint #004
Define Run Sprint Decide
62% complete · Next session May 21 (Decide)
Session Log
Shared Documents
3 files
Output Package
Your outputs
Unlocks after the Decide session (May 21)
Available as individual PDFs on May 21
Messages
1 new
Advisor A · May 14, 11:32 AM
"Good session today. I've updated the direction doc with the three positioning options. Review before May 21."
Dashboard
✓ Sprint CompleteCompleted May 21
🧭 Strategic Clarity Sprint Complete
YOUR SPRINT IS COMPLETE.

Not a generated framework. A real position, built with someone who has been in this room before.

Your Outputs
4 documents ready
How did we do?
How likely are you to recommend Who's Who to someone you know?
1
2
3
4
5
6
7
8
9
10
What's your next moment?
Or: Partner with us
Accelerator Partnership
Bring Who's Who to your portfolio, cohort, or leadership team. From $6K/month.
Explore partnership →
KNOW SOMEONE WHO'S STUCK?

"Stop stressing and start texting someone who actually knows what they're doing."

Career Sprint · Intake
LET'S BUILD YOUR BRIEF.
Next steps
LET'S TALK
IT THROUGH.

Not ready for the full brief yet? Leave your details and we'll reach out to set up a short intro call — to understand where you are and point you to the right next step.

A 30-minute call with an advisor, not a sales pitch.
We'll help you scope the right sprint for your situation.
Confidentiality is a default, not an option.
Intro call
Tell us how to reach you
What's on your mind?
Where you are
Finding the right opportunity Testing a concept Ongoing innovation support Handover & scale AI implementation Not sure yet
Timeline
This quarter Next quarter Just exploring
No commitment — just a conversation. We'll reach out within 24 hours.
What happens next
Typically replies within 24 hours
1
We review your request personally — a real advisor, not an autoresponder.
2
We set up a short intro call to understand where you are.
3
We point you to the right sprint for your situation — or simply give you clarity.
Common questions
How long does a sprint take?
Most run four weeks. Design and advisory engagements can run four to eight, depending on scope — we confirm the exact shape on the intro call.
What does it cost?
Each sprint is scoped and priced as a fixed engagement after the intro call — never hourly. You'll know the number before anything starts.
Do you sign NDAs?
Always. Confidentiality is a default, not an option — we work inside sensitive problems and treat them that way.
What if I don't know what I need yet?
That's exactly what the intro call is for. We'll help you frame the problem and point you to the right starting point — even if that's not us.
Who will I actually talk to?
A senior advisor who has built before — not a junior account manager. The people who scope your work are the people who do it.
About Who's Who

BUILT ON
INSTINCT.
BACKED BY
EXPERIENCE.

We build what others only advise. A cross-functional team embedded in your problem, identifying, designing, and shipping innovation in weeks, not quarters.

SALWA RADWI
Founder · Who's Who

Salwa has built ventures across the MENA region, some that didn't make it, and some that did. Each one taught her something different about what it actually takes to build in this part of the world.

The pattern was never the strategy deck or the market analysis. The constraint was always the same: not enough people who could both think and build. Senior enough to see the problem clearly. Hands-on enough to actually solve it.

Who's Who is what she kept wishing had existed, a team you could bring in on a specific problem, with a defined scope and a real output at the end. Not advice. Not a slide. Something you can ship.

She built it for the organisations navigating their next hard moment, the ones that can't afford to move slowly, but also can't afford to get it wrong.

Salwa Radwi
WHAT WE
BELIEVE.
01
Execution beats advice, every time.
A strategy deck that sits in a folder is worth nothing. Everything we do ends in something you can ship, test, or run, not read.
02
The right team has built it before, in the real world.
Theoretical expertise is easy to find. We bring people who have navigated this specific problem in this specific market, and can move fast because they've made the mistakes already.
03
Confidentiality is a default, not a feature.
What you're building stays between us. We're embedded inside your problem, that requires trust, and trust requires discretion. Real challenges need real honesty.
04
Sprints respect everyone's time.
No open-ended retainers. No scope that drifts. Every sprint has a defined problem, a fixed timeline, and a real output at the end. You know what you're getting before we start.
05
This region builds differently, and that's an advantage.
The MENA market has constraints, nuances, and opportunities that Western playbooks don't cover. We build for the context you're actually in, not the one the case studies assume.
06
Innovation is a muscle, not a moment.
One sprint delivers one output. But the process of running sprints, finding, designing, building, automating, is how organisations build the capability to keep moving. We're here for both.
READY TO
BUILD SOMETHING?
In the Lab

WHAT WE'VE
BEEN BUILDING.

Real engagements. Real outputs. A look inside the problems we've been embedded in and what came out the other side.

ADVISORY
Advise
Outlier Ventures
INNOVATION
ADVISORY
Embedded strategic advisory for one of the world's leading Web3 accelerators, helping portfolio companies navigate product-market fit in emerging tech markets.
Read more
BUILD
Discover · Design
Milk Network
BUILDING
MOO
From blank brief to working product, we ran discovery, mapped the opportunity, designed the experience, and shipped the first version of MOO, Milk's community-first platform.
Read more
DESIGN
Design · Automate
STC
THE SARIHA
PROJECT
A full concept-to-implementation sprint inside STC's innovation arm, identifying the right problem, designing the service, and delivering a production-ready build.
Read more
Outlier Ventures · Advisory
ADVISORY
Outlier Ventures
INNOVATION
ADVISORY
One of the world's leading Web3 accelerators needed strategic clarity at the portfolio level, not generic advice, but embedded thinking alongside their team.
The Brief
Outlier Ventures runs accelerator programmes for early-stage Web3 and deep tech companies. As the sector matured and founders faced increasingly complex go-to-market questions, they needed a strategic thinking partner who could sit alongside their team, not a consultant with a deck, but someone embedded in the day-to-day problem.
What We Did
We ran an ongoing advisory engagement across multiple portfolio cohorts, working directly with founders on positioning, product-market fit strategy, and go-to-market sequencing. We also advised the Outlier team on programme structure and how to identify which portfolio companies needed intervention at what stage.
The Output
A repeatable advisory framework used across cohorts, individual company strategy documents, and a clearer internal methodology for Outlier's team to identify and prioritise where strategic support was needed most.
Milk Network · Discover · Design
MOO
Milk Network
BUILDING
MOO
Milk had a clear sense that their community needed a digital home, but no brief, no spec, and no product team. We were brought in from zero.
The Brief
Milk Network is a creative and cultural community with a growing membership base. They knew something needed to exist, a platform, a space, something, but hadn't defined what it was or whether their audience would pay for it. They needed the thinking and the building done together.
What We Did
We started with a discovery sprint, interviewing members, mapping the opportunity space, and stress-testing several product directions. From there we moved directly into design: wireframes, prototype, user testing. We handed off a validated concept and a working first version of MOO, their community platform, ready for onboarding.
The Output
MOO, a community-first platform built for the Milk Network audience. Validated concept, working product, onboarding flow, and a product roadmap with clear priorities for the next 6 months.
STC · Design · Automate
SARIHA
STC
THE SARIHA
PROJECT
Inside STC's innovation function, we were given a problem space and asked to come back with something real. Eight weeks later, we did.
The Brief
STC's innovation team had identified a space worth exploring, a service opportunity sitting at the intersection of their infrastructure and an underserved customer segment. The brief was deliberately open: explore the space, find the right problem, and build something that proves the concept.
What We Did
We ran a full sprint from problem definition through to a production-ready implementation. Discovery and stakeholder interviews in weeks one and two. Concept design and prototype validation in weeks three and four. Build and integration in weeks five through eight. The team worked embedded inside STC's environment throughout.
The Output
Sariha, a service concept with a validated market, a working implementation, and a handover package that included technical documentation, a go-to-market brief, and a recommended roadmap for the first 90 days post-launch.
Join the Network
ARE YOU
WHO WE'RE
LOOKING FOR?

We're building the most trusted advisory network in the region. If you've operated at the top of your field, and you know what it takes, we want you in the room.

10+ years operating at a senior level
Deep MENA market knowledge or C-suite track record
Available for 3–4 focused sessions per engagement
Willing to give the real read, not the comfortable one
All advisors sign NDA before seeing any client brief
Advisor Waitlist
Apply to join. We review every application personally.
Areas of expertise — select all that apply
Business Function
Strategy Growth Operations Finance / CFO Sales Marketing Product People & Talent Legal & Compliance
Industry
B2B SaaS FMCG / Retail Real Estate Healthcare Fintech E-commerce Logistics Media & Entertainment Education Government / Public Sector
Specialisation
Fundraising M&A / Exits Market Entry Turnarounds Scaling Family Business Venture / PE Go-to-Market Board Advisory
Market Experience
UAE KSA Egypt Qatar Kuwait Bahrain Jordan / Levant North Africa Global
You'll hear from us within 5 days.
Get in touch
Got something specific?
Drop it here.

Not every problem needs a four-week sprint. If you have a quick question, a decision to pressure-test, or just want to know if we're the right fit, send it through. We read everything.

A specific question you need answered fast
A decision you want a second opinion on
Not sure what you need, just want to talk
What do you need?
How urgent is this?
This week Within a month No rush

We respond within 24 hours.

فلسفة · Falsafa
THINKING OUT LOUD.

Ideas, observations, and uncomfortable questions about innovation, organisations, and what it takes to build something real.

Product · Decision-making

The Prototype Test: How to Get Real Signal Before You Commit the Budget

Most organisations have too many ideas and not enough clarity on which one to back. The result is usually paralysis or overcorrection. There is a middle path.

June 2025 READ →
Family Business · Saudi Arabia

Family Businesses and the Innovation Paradox

The organisations most at risk from the current pace of change are often the slowest to respond to it. This is not a character flaw. It is a structural one.

June 2025 READ →
Government · Public Sector

When Government Entities Build: Lessons from Public Sector Innovation Sprints

Government entities must innovate visibly while maintaining operational continuity millions depend on. That tension shapes everything — and understanding it is necessary for understanding why government innovation is so often slower than it should be.

June 2025 READ →
Strategy · Method

The 90-Day Test: Sprint vs. Consulting Engagement

Consultants do valuable work. But there is a category of work that consulting engagements consistently fail to deliver on — and that category is building something new.

June 2025 READ →
Strategy · Saudi Arabia

The Hidden Cost of Waiting: What "We'll Start Next Quarter" Actually Costs

There is a calculation almost no organisation makes explicitly, but every organisation makes implicitly every time it defers a decision to build something new.

June 2025 READ →
Organisation · Talent

Hiring vs. Embedding: The Real Options for Building Innovation Capability

The default answers — hire someone, bring in a consultancy, task an internal team — each fail in predictable ways. Understanding why helps organisations stop defaulting and start choosing.

June 2025 READ →
7 essays published More coming.
Strategy June 2025

Why Most Innovation Budgets in Saudi Arabia Produce Slides, Not Products

There is a pattern that repeats itself across boardrooms in Riyadh, Jeddah, and every major city in between.

A leadership team identifies a real problem — a digital gap, a process that no longer works, a market shift they need to respond to. They commission a study, bring in a consultancy, or task an internal team to investigate. Several months later, a polished presentation lands on the table. The analysis is thorough. The frameworks are recognisable. The recommendations are sensible.

And then, more often than not, nothing ships.

This is not a Saudi problem. It is not even a MENA problem. But it is particularly visible here, where the pace of transformation demanded by Vision 2030 is colliding with organisational structures that were built for a different era. The gap between ambition and execution is wide — and the slide deck has become the default way of filling it without actually closing it.

Why the slide deck keeps winning

The slide deck wins for understandable reasons. It is fast to produce relative to building something real. It creates the appearance of progress without requiring the organisation to commit to a direction. It travels well through approval layers. And crucially, it carries no accountability — a recommendation on a slide cannot fail in the way that a product can.

But the cost of that safety is significant. Every week spent debating a framework is a week not spent learning from a real user. Every SAR allocated to market analysis is a SAR not testing whether the hypothesis is actually true. The slide deck optimises for internal comfort, not for finding out if the thing you are trying to build will work.

The deeper problem is that most organisations treat innovation as a question to be answered, not a capability to be built. They fund research when they should fund experiments. They hire advisors when they should hire builders. They seek consensus before they seek signal.

The approval cycle as the real bottleneck

In many Saudi organisations — corporates, government entities, family businesses — the innovation bottleneck is not ideation. Most leadership teams can name three things they know they should be doing differently. The bottleneck is the distance between "we think this is the right direction" and "we have evidence that it is."

That distance is usually filled by more analysis, more presentations, more rounds of alignment. And each round adds time and removes momentum without bringing the organisation any closer to knowing whether the idea is actually worth building.

The companies that move fastest are not the ones with the best strategies. They are the ones that have learned to treat a prototype as a question, not a commitment. They build the smallest possible version of the thing and put it in front of real people, not to launch it, but to find out what they do not yet know. That feedback loop — brief, build, learn, decide — is faster and cheaper than any research methodology.

What this looks like in practice

A government entity in the region spent two years debating the specification for an internal platform. Every stakeholder had a perspective. Every perspective was valid. The debate had no natural ending point because the debate was happening in the abstract — without a real thing to react to.

An external team came in, ran a four-week sprint, and produced a working prototype. Not a wireframe. Not a concept. A functional prototype that could be clicked through by the people who would actually use it. The internal debate that had lasted two years was resolved in three weeks of user feedback.

The prototype did not answer every question. But it answered the most important ones — whether the core interaction made sense to real users, whether the assumptions the team had built into the spec were correct, and which of the competing stakeholder positions actually mattered to the end user. Nothing about that outcome required a larger budget or a more talented team. It required a different approach: build something, then decide.

The question worth asking

The useful diagnostic for any organisation is not "do we have an innovation strategy?" Most do, at least on paper. The more honest question is: What is the last thing we built and put in front of a real user?

Not presented internally. Not submitted for approval. Actually put in front of the person it was designed for, and observed.

If the answer is measured in years rather than weeks, the problem is not the strategy. The problem is the distance between the room where decisions are made and the evidence that should be informing them.

Closing that distance does not require a new innovation function, a dedicated team, or a multi-year transformation programme. It requires a different decision at the beginning of the next project: to build something real before committing to building the whole thing.

The slide deck is a useful tool. But it should be the output of a sprint, not the substitute for one.

هناك نمط يتكرر في قاعات الاجتماعات في الرياض وجدة وكل مدينة كبرى بينهما.

تحدد الفرق القيادية مشكلة حقيقية — فجوة رقمية، أو عملية لم تعد تؤدي غرضها، أو تحول في السوق يحتاجون إلى الاستجابة له. يطلبون دراسة، أو يستعينون بشركة استشارية، أو يكلفون فريقاً داخلياً بالتحقيق. بعد أشهر عدة، يصل عرض تقديمي مصقول إلى الطاولة. التحليل شامل. الأطر المستخدمة مألوفة. التوصيات منطقية.

ثم، في أغلب الأحيان، لا يُشحن شيء.

هذه ليست مشكلة سعودية. وليست مشكلة المنطقة. لكنها واضحة بشكل خاص هنا، حيث تتصادم وتيرة التحول التي تتطلبها رؤية 2030 مع الهياكل التنظيمية التي بُنيت لعصر مختلف. الهوة بين الطموح والتنفيذ واسعة — وأصبح عرض الشرائح الوسيلة الافتراضية لسدها دون إغلاقها فعلياً.

لماذا تفوز شريحة العرض دائماً

تفوز شريحة العرض لأسباب مفهومة. إنها أسرع في الإنتاج مقارنةً ببناء شيء حقيقي. تخلق وهم التقدم دون أن تُلزم المؤسسة بتوجه محدد. تنتقل بسهولة عبر طبقات الاعتماد. والأهم من ذلك، أنها لا تحمل أي مساءلة — فالتوصية على الشريحة لا يمكنها أن تفشل بالطريقة التي يفشل بها المنتج.

لكن تكلفة تلك السلامة باهظة. كل أسبوع يُقضى في مناقشة الأطر هو أسبوع لا يُستفاد فيه من مستخدم حقيقي. وكل ريال مخصص للتحليل السوقي هو ريال لا يُختبر فيه ما إذا كانت الفرضية صحيحة.

المشكلة الأعمق هي أن معظم المؤسسات تتعامل مع الابتكار باعتباره سؤالاً يحتاج إجابة، لا قدرة تحتاج بناء. تموّل البحث حين ينبغي لها تمويل التجارب. توظّف المستشارين حين ينبغي لها توظيف البنّائين.

دورة الاعتماد باعتبارها العقبة الحقيقية

في كثير من المؤسسات السعودية، سواء أكانت شركات أم جهات حكومية أم أعمالاً عائلية، لا تكمن عقبة الابتكار في توليد الأفكار. معظم الفرق القيادية تستطيع تسمية ثلاثة أشياء تعرف أنها ينبغي أن تفعلها بشكل مختلف. العقبة هي المسافة بين "نعتقد أن هذا الاتجاه صحيح" و"لدينا دليل على صحته".

الشركات الأسرع حركةً ليست تلك التي تمتلك أفضل الاستراتيجيات، بل تلك التي تعلّمت التعامل مع النموذج الأولي باعتباره سؤالاً لا التزاماً. تبني أصغر نسخة ممكنة وتضعها أمام أشخاص حقيقيين، ليس للإطلاق، بل لاكتشاف ما لا تعرفه بعد.

كيف يبدو ذلك في الواقع العملي

أمضت جهة حكومية في المنطقة عامين في مناقشة مواصفات منصة داخلية. لكل صاحب مصلحة منظوره. كل منظور صحيح. لم يكن للنقاش نهاية طبيعية لأنه كان يجري في الفضاء المجرد — دون شيء حقيقي يمكن التفاعل معه.

جاء فريق خارجي وأجرى سباقاً مدته أربعة أسابيع وأنتج نموذجاً أولياً فعلياً. ليس إطاراً سلكياً. ليس مفهوماً. بل نموذجاً وظيفياً يمكن النقر عليه من قِبل من سيستخدمونه فعلاً. النقاش الداخلي الذي امتد عامين حُسم في ثلاثة أسابيع من تعليقات المستخدمين.

السؤال الجدير بالطرح

المقياس المفيد لأي مؤسسة ليس "هل لدينا استراتيجية ابتكار؟" معظمها لديها، على الورق على الأقل. السؤال الأكثر صدقاً هو: ما آخر شيء بنيناه ووضعناه أمام مستخدم حقيقي؟

شريحة العرض أداة مفيدة. لكنها ينبغي أن تكون ناتج سباق، لا بديلاً عنه.

Who's Who is an embedded innovation arm for companies that need to move. We map opportunities, design concepts, and ship working capability — in weeks, not quarters.

Product Decision-making June 2025

The Prototype Test: How to Get Real Signal Before You Commit the Budget

Most organisations have a version of the same problem: too many ideas, not enough clarity on which one to back. The result is usually one of two failure modes — paralysis (nothing moves because no one can agree) or overcorrection (a large budget committed to the wrong thing before anyone had evidence it would work).

There is a middle path. It is not complicated, but it requires a shift in how decisions get made.

The question that unlocks it

The most useful question an organisation can ask before committing to a build is not "do we believe this will work?" It is: what would have to be true for this to work — and how cheaply can we test it?

That reframe changes the entire shape of the decision. Instead of asking leadership to approve or reject an idea based on analysis, you are asking them to approve a small, fast test designed to produce real evidence. That is a much easier conversation, and it produces much better outcomes.

What a prototype is actually for

A prototype is not a scaled-down version of the final product. It is a device for answering a specific question.

If the question is "will users understand what this does," you need something they can click through. If the question is "will this process actually save time," you need something that can be run against real work. If the question is "is this a problem people will pay to solve," you need to find out whether they will pay — not whether they say they will.

The prototype you build should be the cheapest possible thing that answers the most important unknown. Nothing more.

A team in the region built a community platform for a media brand. Before writing a line of code, they tested the core experience with a set of Figma screens and a WhatsApp group. The signal they got in two weeks of informal testing changed the entire direction of the product. That two weeks saved six months.

Where organisations get this wrong

The most common mistake is building the prototype to impress rather than to learn. This happens when the prototype is shown to leadership instead of users, when it is polished before it is tested, or when the team is emotionally invested in a particular outcome.

A prototype shown only internally is not a prototype. It is a presentation with more effort in it.

The second common mistake is running the test without a clear decision attached to it. If you do not know in advance what the test result would need to look like for you to proceed, you will find a way to proceed regardless. Define the bar before you run the test.

The practical implication

For most organisations in Saudi Arabia right now, the constraint is not ambition or access to ideas. It is the ability to move from "we think this is right" to "we have evidence this is right" without spending six months getting there.

The prototype test is how you do that. It does not require a dedicated team, a new function, or a significant budget. It requires a willingness to build something rough, put it in front of people who will be honest with you, and let the answer change what you do next.

That last part is the hardest. But it is also the only part that matters.

Who's Who runs concept design sprints that move from opportunity to tested prototype in four to six weeks. Real signal before you commit the budget.

Family Business Saudi Arabia June 2025

Family Businesses and the Innovation Paradox: Why the Organisations That Need It Most Are the Slowest to Start

Family businesses are the backbone of the Saudi economy. They account for a significant share of private sector employment, hold deep relationships with customers built across decades, and carry institutional knowledge that no startup can replicate. They also, in many cases, are the organisations most at risk from the current pace of change — and the slowest to respond to it.

This is not a character flaw. It is a structural one.

Why family businesses are uniquely exposed

The competitive advantages that made family businesses dominant in Saudi Arabia — trusted relationships, patient capital, sector depth, access to government — are all real. But they were built in a market where barriers to entry were high and the pace of change was manageable.

Digital-native competitors operate under different constraints. They have no legacy infrastructure to protect, no long-standing customer relationships to preserve, and no family dynamics to navigate. They can move fast precisely because they have nothing to lose.

The result is a category of well-established, well-resourced organisations watching their market being redrawn by companies a tenth of their size — and finding it genuinely difficult to respond at the same speed.

The structural reasons

The first is decision concentration. In most family businesses, significant decisions require family consensus or the approval of a principal who is managing the entire business simultaneously. This is appropriate for large capital decisions. It is fatal for the kind of iterative, experimental work that building new capabilities requires.

The second is talent friction. Hiring the kind of people who can build new things inside an existing organisation requires a different value proposition than the one most family businesses offer. The people who are good at this tend to want autonomy, fast feedback loops, and a culture that tolerates failure. Family businesses often cannot offer that — not because they do not want to, but because their operating model was not built around it.

The third is legacy system complexity. The same infrastructure that makes a family business operationally reliable makes it hard to change quickly. Process changes require cross-departmental buy-in. Technology changes require custom integration. What looks like a small product decision becomes a large organisational project.

What the ones that are moving have in common

The family businesses in the region making real innovation progress have not solved all of these structural problems. They have worked around them.

Specifically: they have separated the innovation work from the core business, given it a defined scope and a fixed timeline, and brought in people from outside the family and outside the organisation to run it. Not permanently — temporarily. Long enough to ship something real, prove the concept, and build the capability that the internal team can then sustain.

The output of that work is not just a product. It is evidence that the organisation can build, and a process for doing it again. That evidence changes the internal conversation in a way that a strategy document never can.

The question for family business leadership

The relevant question is not whether to innovate. Every family business leader in Saudi Arabia already knows the answer to that. The relevant question is whether the organisation's current structure allows it to actually build something new — or whether it is optimised exclusively for protecting and operating what already exists.

If the honest answer is the second, the fix is not a transformation programme. It is a defined sprint, a specific problem, and a team empowered to solve it without navigating the full organisational machine to do so.

The businesses that are most at risk are not the ones that lack ambition. They are the ones that have been planning to start for longer than they intended.

Who's Who works with family businesses that need to move on a specific problem — without the overhead of building an innovation function from scratch.

Government Public Sector June 2025

When Government Entities Build: Lessons from Public Sector Innovation Sprints in the Region

Government entities in Saudi Arabia are under a specific kind of pressure that private sector organisations are not. They must innovate visibly — their transformation is part of a national story — while simultaneously maintaining the operational continuity that millions of people depend on. That tension shapes everything about how they build, and understanding it is necessary for understanding why government innovation is so often slower than it should be.

The good news is that there are genuine lessons from the government entities in the region that are managing to move. They are worth unpacking.

Why the default doesn't work

The standard model for government technology projects — large RFP, long procurement process, vendor delivery, internal sign-off — was designed for infrastructure, not innovation. It assumes the problem is fully understood before the solution is scoped. It externalises risk to a vendor who has no stake in whether the output is actually used. And it produces systems that reflect what stakeholders said they wanted, rather than what users actually need.

The result is a generation of government digital projects that work as specified and fail in practice. Systems that are technically delivered and functionally abandoned. Platforms that went live and never scaled.

This is not primarily a technology problem. It is a method problem.

What works differently

The government entities making real progress have changed two things.

First, they have separated exploration from delivery. The question "should we build this, and what should it be?" is handled separately from "how do we build it at scale?" The first question is answered through rapid prototyping with real users. Only when the answer is yes — validated by evidence, not consensus — does the project enter formal procurement and delivery.

This sounds obvious. It is still rare.

Second, they have brought external teams inside for the exploration phase rather than managing it through a procurement process. Not as vendors accountable to a specification, but as embedded collaborators accountable to an outcome. The distinction matters because the work of discovery and prototyping requires the kind of rapid, iterative decision-making that a vendor relationship is structurally unable to support.

What the private sector can learn

Government innovation sprints, done well, produce a body of learning that private sector organisations rarely capture: what happens when you design for a user who has no choice, has limited digital literacy, and is interacting with your system under stress.

That design constraint produces rigour. A government service that fails is not abandoned by the user — it creates a complaint, a queue, an escalation. The feedback loop is immediate and honest in a way that consumer product feedback rarely is.

Private sector teams that have worked inside government projects tend to be significantly better at designing for edge cases, for low-bandwidth environments, and for users who are not power users. Those skills transfer.

The common denominator

Across the government entities in the region that have managed to ship something meaningful — not a pilot that quietly ended, but a live service that real people use — the common thread is not the technology stack or the vendor. It is the presence of someone inside the organisation willing to own the outcome, not just the process.

That person exists in most government entities. They are often not in the right role, not given the right mandate, and not supported with the right method. The structural answer to that is less complicated than it sounds: give them a defined scope, a fixed timeline, an external team to work with, and the authority to make decisions without routing every one of them through a committee.

The organisations that have done that are building. The ones that have not are still in the planning phase.

Who's Who has run sprints inside government entities across the region. We know what it takes to move inside a complex stakeholder environment and still ship something real.

Strategy Method June 2025

The 90-Day Test: What a Real Innovation Sprint Looks Like vs. a Consulting Engagement

This is not a critique of consulting. Consultants do valuable work. Strategy, benchmarking, transformation roadmaps, regulatory navigation — there are problems that are genuinely best solved by an experienced firm with broad pattern recognition and the credibility to present to a board.

But there is a category of work that consulting engagements consistently fail to deliver on, and that category is building something new. Understanding why is useful — not to dismiss consulting, but to know when to use which tool.

What consulting engagements are optimised for

A consulting engagement is, structurally, a research and recommendation exercise. The firm is hired to analyse a situation, develop options, and present a recommended path. The deliverable is a document or a presentation. The accountability ends at the point of delivery.

This structure works well for problems where the question is "what should we do?" and the answer requires breadth of knowledge, market data, and benchmarking across industries. It works poorly for problems where the question is "does this actually work?" and the answer requires building something and finding out.

The difference is not the quality of the firm. It is the nature of the output they are contracted to produce.

What a sprint is optimised for

A sprint is a short, fixed-scope engagement with a defined output that is not a document. It is a validated prototype, a working system, a tested concept, or a production-ready build.

The structure is different in every important way. The team is embedded inside the problem rather than observing from outside it. The output is something that can be used rather than something that can be read. The accountability extends past delivery because the thing that was built either works or it does not.

Sprints are optimised for the moment when you need to know if something is real — not whether it is a good idea, but whether it actually functions in the real world with real users and real constraints.

Where organisations get confused

The confusion typically happens at the point of scoping. An organisation has a challenge — a process that is broken, a product it needs to build, a market it needs to enter. It reaches for the familiar tool: a consulting engagement.

The consultancy returns three months and several hundred thousand riyals later with a detailed strategy for addressing the challenge. The strategy is correct. The organisation still does not know how to build the thing. And the window in which the problem needed to be solved has sometimes already closed.

The same budget, applied to a sprint, would have produced a tested prototype, real user feedback, and a build-ready brief. Neither outcome is wrong. They are answers to different questions. The error is using a research tool when you need a building tool.

A practical distinction

A useful heuristic: if the output you need could be presented as a slide deck, commission a consulting engagement. If the output you need has to be clicked through, used, or deployed to be meaningful — that is a sprint.

Most organisations need more of the second type of work and default instead to the first, because the first is familiar, credentialled, and carries less immediate risk. The irony is that the second type, done well, is the one that actually reduces risk — because it produces evidence before you commit a large budget to a direction that has not been tested.

The 90-day question

The test is simple: in the next 90 days, what do you want to have built, tested, and decided on — not studied, not recommended, not presented?

If you can answer that question with specificity, you probably need a sprint, not a strategy engagement. The two are not mutually exclusive, but they are not interchangeable either.

هذا ليس نقداً للاستشارة. المستشارون يقومون بعمل قيّم. الاستراتيجية، والمقارنة المرجعية، وخرائط طريق التحول، والتوجيه التنظيمي — هناك مشكلات تُحلّ حقاً بشكل أفضل من خلال شركة متخصصة لديها نمط تعرف واسع النطاق.

لكن هناك فئة من العمل تفشل الاستشارات باستمرار في تقديمها، وهذه الفئة هي بناء شيء جديد. فهم السبب مفيد — ليس لرفض الاستشارة، بل لمعرفة متى تستخدم أي أداة.

ما تُحسَّن الاستشارة من أجله

تكليف الاستشارة هو، من الناحية الهيكلية، تمرين بحث وتوصية. الشركة مُوظَّفة لتحليل الوضع وتطوير الخيارات وتقديم مسار موصى به. المخرج هو وثيقة أو عرض تقديمي. تنتهي المساءلة عند نقطة التسليم.

هذا الهيكل يعمل بشكل جيد للمشكلات التي يكون فيها السؤال "ماذا يجب أن نفعل؟" ويتطلب الجواب اتساع المعرفة وبيانات السوق. يعمل بشكل سيء للمشكلات التي يكون فيها السؤال "هل هذا يعمل فعلاً؟"

ما يُحسَّن السباق من أجله

السباق هو تعاون قصير محدد النطاق بمخرج محدد ليس وثيقة. إنه نموذج أولي مُتحقَّق منه، أو نظام عامل، أو مفهوم مختبر، أو بناء جاهز للإنتاج.

الهيكل مختلف في كل نقطة مهمة. الفريق مدمج داخل المشكلة لا يراقبها من الخارج. المخرج شيء يمكن استخدامه لا شيء يمكن قراءته. المساءلة تمتد بعد التسليم.

سؤال التسعين يوماً

الاختبار بسيط: في التسعين يوماً القادمة، ما الذي تريد أن يُبنى ويُختبر ويُقرَّر بشأنه — لا يُدرَّس، لا يُوصى به، لا يُعرَض؟

إن كان بإمكانك الإجابة على هذا السؤال بتحديد، فأنت على الأرجح تحتاج سباقاً لا تعاقد استشاري. الاثنان ليسا متنافيَين، لكنهما ليسا قابلَين للتبادل.

Who's Who runs sprints, not consulting engagements. Four to six weeks, real output at the end, team embedded inside your problem from day one.

Strategy Saudi Arabia June 2025

The Hidden Cost of Waiting: What "We'll Start Next Quarter" Actually Costs Saudi Businesses

There is a calculation that almost no organisation makes explicitly, but that every organisation is making implicitly every time it defers a decision to build something new.

The calculation is simple: what does it cost to not start today? Not in the abstract — in riyals, in customers, in market position.

Most leadership teams have a strong instinct for the cost of moving too fast. They have seen projects fail, budgets wasted, initiatives launched before they were ready. The risk of premature action is concrete, recent, and memorable.

The cost of waiting is different. It is diffuse, compounding, and invisible until it is too late to reverse.

How opportunity cost actually compounds

When a Saudi retailer decides to delay its digital loyalty programme by one quarter, it is not just deferring one quarter of programme revenue. It is deferring the data it would have accumulated, the customer behaviours it would have learned, the operational muscle it would have built, and the competitive positioning it would have established.

The competitor that launched three months earlier is not just three months ahead. It is three months of learning ahead. In a market moving as fast as this one, that gap is not linear — it compounds.

This is true across sectors. The healthcare provider that delays its patient experience improvement. The government entity that defers its digital service migration. The family business that keeps planning the e-commerce launch. Each quarter of delay is not a neutral pause — it is an active choice to let the gap widen.

Why the calculation is hard to make

The reason organisations do not make the opportunity cost calculation explicitly is that it requires imagining a future that did not happen. The cost of the project that ran over budget is in the accounts. The cost of the customer you lost to a competitor because your service was inferior is not.

This asymmetry means that the default bias in most organisations is toward caution. The visible risks of action are scrutinised; the invisible risks of inaction are not.

Finance teams are excellent at modelling the cost of investment. Very few have a process for modelling the cost of deferral. And without that model on the table, the default will always be to wait for more information, more alignment, more certainty — even when the window is closing.

A framework for making it visible

The question to ask is not "what will this project cost?" but "what is the cost per month of not having this capability?"

For most organisations, that calculation requires three inputs: the revenue or efficiency impact of the capability once live, the time it takes to build it, and the rate at which the competitive landscape is moving. None of these numbers are precise, but all of them are estimable — and putting even rough figures against them changes the conversation.

A capability worth 2 million SAR per month in recovered revenue, requiring three months to build, costs 6 million SAR per month of delay to defer. That is a different conversation than "we should start this eventually."

The companies that move

The organisations in Saudi Arabia making the most progress right now are not the ones with the highest risk appetite. They are the ones that have learned to be rigorous about both sides of the ledger — the cost of action and the cost of inaction — and make decisions accordingly.

They have also learned that the fastest way to reduce the cost of action is to scope it tightly. A four-week sprint to validate one assumption costs a fraction of a six-month project to build the full thing. The right response to risk is not waiting — it is finding the smallest version of the test that produces the signal you need to proceed.

Next quarter is always four weeks away. And four weeks from now, the calculation will look the same.

هناك حساب لا تجريه أي مؤسسة تقريباً بشكل صريح، لكن كل مؤسسة تجريه ضمنياً في كل مرة تؤجل قراراً ببناء شيء جديد.

الحساب بسيط: ما تكلفة عدم البدء اليوم؟ ليس بشكل مجرد — بل بالريال، وبالعملاء، وبالموقع في السوق.

تكلفة الانتظار مختلفة. إنها مبهمة، ومركّبة، وغير مرئية حتى يصبح الوقت متأخراً جداً على التراجع.

كيف تتراكم تكلفة الفرصة فعلاً

حين يقرر تاجر سعودي تأجيل برنامج الولاء الرقمي ربعاً واحداً، فهو لا يؤجل ربع السنة فقط من إيرادات البرنامج. يؤجل البيانات التي كان سيراكمها، وسلوكيات العملاء التي كان سيتعلمها، والعضلات التشغيلية التي كان سيبنيها.

المنافس الذي أطلق قبل ثلاثة أشهر ليس متقدماً بثلاثة أشهر فقط. إنه متقدم بثلاثة أشهر من التعلم. في سوق يتحرك بهذه السرعة، هذه الفجوة ليست خطية — بل تتراكم.

لماذا الحساب صعب الإجراء

السبب في أن المؤسسات لا تجري حساب تكلفة الفرصة بشكل صريح هو أنه يتطلب تخيّل مستقبل لم يحدث. تكلفة المشروع الذي تجاوز الميزانية موجودة في الحسابات. تكلفة العميل الذي خسرته للمنافس ليست كذلك.

الفرق بين الحالتين يعني أن التحيّز الافتراضي في معظم المنظمات هو نحو الحذر. مخاطر الفعل المرئية تُدقَّق فيها؛ مخاطر عدم الفعل غير المرئية لا تُدقَّق فيها.

إطار لجعل الأمر مرئياً

السؤال المطلوب ليس "ما تكلفة هذا المشروع؟" بل "ما تكلفة الشهر من عدم امتلاك هذه القدرة؟"

قدرة تساوي 2 مليون ريال شهرياً في الإيرادات المستردة، وتتطلب ثلاثة أشهر للبناء، تكلّف 6 ملايين ريال عن كل شهر تأخير. هذا حوار مختلف عن "ينبغي لنا البدء في هذا في النهاية."

الربع القادم يبعد دائماً أربعة أسابيع. وبعد أربعة أسابيع، سيبدو الحساب كما هو.

Who's Who helps organisations move on specific problems with a fixed scope and a real output. We start within two weeks of your brief.

Organisation Talent June 2025

Hiring vs. Embedding: The Real Options for Building Innovation Capability in a Growing Organisation

When a leadership team decides it is serious about building something new, there is an immediate secondary question that rarely gets examined carefully enough: who is going to do it?

The default answers are hire someone, bring in a consultancy, or task an internal team. Each of these options is chosen for understandable reasons. Each of them fails in predictable ways for a specific category of problem. Understanding why helps organisations stop defaulting and start choosing.

The four paths

Hire full-time. The logic is sound: if this capability matters, build it properly with dedicated people who are accountable to the organisation long-term. The failure mode is that hiring takes time, the right people are hard to find in a market that is competing aggressively for them, and new hires spend their first months learning the organisation rather than building in it. For a problem that needs to move now, full-time hiring is structurally too slow.

Engage a consultancy. Credentialled, fast to mobilise, and appropriate for strategy and analysis work. The failure mode is delivery: consultants produce recommendations, not products. When the engagement ends, the organisation has a document and no new capability. The knowledge walks out with the consultant.

Task an internal team. The most common choice, and the one most likely to produce nothing. Not because the team is incapable, but because they are already fully allocated to the work that keeps the business running. Innovation gets staffed with whoever can be partially borrowed from other departments, given an unclear mandate, and asked to move fast without authority.

Embed an external team. Bring in a cross-functional team for a defined scope — inside your organisation, working on your problem, accountable to a real output rather than a report. They move fast because they have no other agenda. They leave when the work is done. The capability they built stays.

Why the fourth option is still underused

The embedded model is underused in the region for reasons that are more about familiarity than merit. Procurement processes are built for vendors who deliver defined specifications, not for teams who co-create outcomes. Leadership teams are more comfortable with the legible deliverable — the report, the strategy — than with the messier accountability of "did something real ship?"

There is also a trust question. Embedding an external team inside an organisation requires a level of access and transparency that feels uncomfortable before the relationship is established. The organisations that have done it well describe the first engagement as the hardest — and the most valuable.

The right option for the right moment

These options are not mutually exclusive across time. The right sequence for most organisations is:

Use an embedded team to ship the first version of something and validate the capability. Use that result to make the case for a full-time hire. Hire the person who maintains and extends what was already built and proven. Engage a consultancy when you need strategic framing or market intelligence, not when you need something built.

The error is using the wrong tool for the current moment. Hiring when you need speed. Consulting when you need building. Tasking an internal team that has no capacity.

The question that clarifies it

I need this specific capability live and tested within 90 days. The person or team doing this work needs to be accountable for whether the output actually works. I do not have the internal capacity to staff it properly, and I cannot wait six months for a hire to onboard.

If that is the situation — and it is the situation for most growing organisations in Saudi Arabia right now — the answer is not a hire, a consultant, or a borrowed internal team.

حين تقرر فرقة قيادية أنها جادة في بناء شيء جديد، هناك سؤال ثانوي فوري نادراً ما يُفحص بعناية كافية: من سيفعل ذلك؟

الإجابات الافتراضية هي توظيف شخص ما، أو الاستعانة بشركة استشارية، أو إسناد المهمة لفريق داخلي. كل من هذه الخيارات يُختار لأسباب مفهومة. وكل منها يفشل بطرق يمكن التنبؤ بها لفئة محددة من المشكلات.

المسارات الأربعة

التوظيف بدوام كامل. المنطق سليم: إن كانت هذه القدرة مهمة، ابنِها بشكل صحيح مع أشخاص متفرغين. نمط الفشل هو أن التوظيف يستغرق وقتاً، والأشخاص المناسبون يصعب إيجادهم، والموظفون الجدد يقضون أشهرهم الأولى في تعلّم المنظمة لا في البناء فيها.

الاستعانة بشركة استشارية. معتمدة، وسريعة التعبئة، ومناسبة لأعمال الاستراتيجية والتحليل. نمط الفشل هو التسليم: المستشارون ينتجون توصيات لا منتجات. حين ينتهي التعاقد، تمتلك المنظمة وثيقة لا قدرة جديدة.

إسناد المهمة لفريق داخلي. الخيار الأكثر شيوعاً، والأكثر احتمالاً لإنتاج لا شيء. ليس لأن الفريق عاجز، بل لأنه مخصص بالكامل للعمل الذي يُبقي الأعمال تعمل.

إدماج فريق خارجي. إحضار فريق متعدد التخصصات لنطاق محدد — داخل مؤسستك، يعمل على مشكلتك، مساءل عن مخرج حقيقي لا تقرير. يتحركون بسرعة لأن ليس لديهم أجندة أخرى. يغادرون حين ينتهي العمل. القدرة التي بنوها تبقى.

الخيار الصحيح للحظة الصحيحة

هذه الخيارات ليست متنافية عبر الزمن. التسلسل الصحيح لمعظم المنظمات هو:

استخدام فريق مدمج لشحن النسخة الأولى وتحقق القدرة. استخدام تلك النتيجة للحصول على موافقة على توظيف موظف دائم. توظيف الشخص الذي يحافظ ويطوّر ما بُني وأُثبت بالفعل.

الخطأ هو استخدام الأداة الخاطئة للحظة الحالية. التوظيف حين تحتاج السرعة. الاستشارة حين تحتاج البناء. إسناد المهمة لفريق داخلي لا طاقة له.

Who's Who is the embedded option. Cross-functional team, defined scope, real output. We start within two weeks and leave when the capability is yours.