by Thomas Lim | Aug 19, 2026
This article is originally published on Forbes on 17 August 2026 []
Imagine a customer raises a complex issue. Today, it may move from customer service to operations, finance, legal and product. Each function reviews its portion, updates its own system and protects its own priorities. By the time the organisation responds, the customer has repeated the story several times and nobody fully owns the outcome.
Now imagine an AI-enabled workflow that gathers the history, identifies policy and financial implications, proposes response options and alerts the people whose judgment is required. No department has disappeared. But the department no longer determines how the work moves.
This is the deeper organisational question raised by AI. The discussion is usually about productivity: which tasks can be automated, how much time can be saved and how many agents can be deployed. AI may make the existing organisational model obsolete. Departments may remain homes for expertise while work increasingly forms around customers, products, strategic priorities and end-to-end outcomes. The leadership challenge is therefore not simply to implement AI. It is to redesign the system of work. Four systems lenses can help.
1. Diagnose How Silos Persist
The Levels of Perspective model distinguishes visible events from patterns, systemic structures and mental models. At the event level, leaders may see delayed approvals, duplicated work or conflicting recommendations. At the pattern level, the same customer issue repeatedly crosses several functions. At the structural level, separate budgets, systems, incentives and reporting lines reinforce fragmentation. Beneath these structures sit assumptions such as “my department must control this decision” or “sharing data creates more risk than value.”
Many AI projects address only the event. They automate a handoff, accelerate an approval or add a chatbot. The symptom improves, but the larger system remains unchanged. Before deploying AI, choose one high-friction outcome and examine it at all four levels. Ask what keeps recurring, which structures produce that pattern and which assumptions make those structures appear reasonable. This prevents the organisation from digitising the silo instead of redesigning it.
2. Manage The Tension Between Today And The Future
Healthy tension helps leaders hold two realities at once: an honest account of current conditions and a compelling view of the future. The current reality may be that customer issues cross five functions, decisions take 10 days and each function is measured separately. The desired future may be a coordinated workflow in which specialist expertise is drawn in when needed and one person remains accountable for the total outcome.
Leaders often reduce the tension in the wrong direction. They lower the vision until it fits the current structure. The new AI workflow then becomes another tool inside the old process. Instead, define the future operating principle before selecting the technology. For example: “Work will be organised around the customer outcome, not the departmental sequence.”
3. Map The Work As A System
A systems view asks leaders to define the larger purpose, identify the essential parts and examine their interdependencies. For an AI-enabled customer resolution system, the parts may include customer service, finance, legal, product, data, risk and the AI platform. The critical question is how tightly their work depends on one another. Some relationships require periodic coordination. Others need continuous information exchange and rapid response. Highly interdependent work should not rely on slow handoffs and occasional meetings.
Map the workflow from beginning to end. Identify where information enters, where judgment is required, where decisions are delayed and where the same data is recreated. Then classify what AI can execute, what it can recommend and what must remain a human decision. This also clarifies the future role of departments. They become capability homes that maintain standards, develop expertise and govern professional quality. Outcome teams draw on those capabilities without being trapped by the departmental boundary.
4. Design For Acceptance And Learning
A technically elegant AI system can still fail if people do not trust it, understand it or see how their role changes. The Q x A = E principle makes this explicit: The quality of the technical solution, multiplied by acceptance by the people, determines the effectiveness of the result.
Acceptance means involving the right people early enough to improve the design, surface risks and build ownership. For each redesigned workflow, clarify who owns the outcome, who sets the guardrails, who may override the system and who is accountable when the result causes harm. Run a bounded pilot around one outcome rather than reorganising the whole company at once.
Do not add a human approval at every stage merely to create a sense of control. That recreates the old bureaucracy in digital form. Human intervention should be concentrated where judgment, ethics, exceptions or material consequences are involved. Then create a feedback loop. Track one leading indicator, one outcome indicator and one balancing indicator. The final question in every review should be: What will we change because of what we have learned?
Get From Faster Silos To A Learning System
AI will not eliminate the need for finance, legal, marketing, human resources or operations. It will challenge the assumption that every piece of work must travel through those functions in sequence. However, the future organisation may operate through a dual structure. Departments preserve expertise and professional standards. Fluid teams combine human judgment, specialist capability and AI agents around an outcome.
This requires leaders to give up an old source of control. Authority can no longer depend mainly on owning information, headcount or process steps. It must come from setting direction, designing conditions, making trade-offs and protecting the integrity of the whole system. This identity shift may prove harder than the technology deployment. Functional leaders must be willing to contribute expertise without defending territory. They may also have to accept that optimising their department can sometimes weaken the performance of the larger organization.
Organisations that merely insert AI into departments may make each silo faster. Those that redesign vision, structures, interdependencies and learning loops around outcomes can become something more valuable: an organisation that works, adapts and learns as one system.
by Thomas Lim | Jul 27, 2026
This article is originally published on Forbes on 24 July 2026 []
Many organisations try to build an innovative culture by encouraging more ideas. They run workshops, create idea portals and appoint innovation champions. These activities can help, but they do not create a sustainable innovation culture.
The real work is more systemic. It is about building a repeatable learning system, and a practical way to do this is to work with two dimensions: architecture and essence.
Architecture is the visible system that supports innovation: roles, processes, platforms, routines, decision rights, metrics, funding, governance and feedback loops. Essence is the human and cultural energy that gives the architecture life: curiosity, reflection, trust, courage, learning, shared purpose and the belief that improvement is part of everyone’s work.
Start With The Innovation Intent
The first step is to clarify the innovation intent. Leaders should avoid vague declarations such as “We need to be more innovative.” That may sound energising, but it does not give people a useful design brief.
Instead, frame questions this way:
- What current pattern is no longer acceptable?
- What customer, employee or stakeholder experience must change?
- What must become easier, faster, safer, more scalable or more meaningful?
This turns innovation from an abstract aspiration into a purposeful act of system redesign.
Nissin’s instant noodle story is a useful example here. The innovation was not simply “make noodles faster.” The deeper intent was to make food convenient, affordable, reliable and accessible with minimal time, tools and skill.
When Nissin later introduced Cup Noodles, the cup was not merely packaging. It became storage, cooking vessel and serving bowl. One design choice removed friction across the whole user journey.
That is the first lesson: Good innovation intent should point to the system that must be redesigned, not only the product or solution that must be produced.
Map The Architecture
Once intent is clear, leaders should map the architecture needed to support it. This means identifying the practical structures that will carry innovation from idea to adoption.
One approach is to map these six elements:
1. Guiding Ideas: What beliefs and principles should shape the innovation effort?
2. Methods And Tools: What frameworks, experiments or practices will people use?
3. Infrastructure: What platforms, forums, data, workflows or resources are required?
4. Skills And Capabilities: What must people learn to do differently?
5. Awareness And Sensibilities: What must people learn to notice?
6. Attitudes And Beliefs: What mindset shifts must be reinforced over time?
Take the Nissin example again. The guiding idea was accessible food. The method involved experimentation with preparation and dehydration. The infrastructure included packaging, manufacturing and distribution. The capability included both production capability and consumer usability. The new awareness was that convenience itself was becoming a form of value. The mindset shift was that prepared food could be practical, respectable and widely adopted.
This is what leaders often miss. They look for the visible product and ignore the surrounding conditions that made adoption possible.
Use This Content Studio Example
The same logic applies inside an organisation. Consider a content studio that needs to produce articles, social posts, podcasts, short videos and campaign assets at scale. A weak innovation response would be to say, “Let’s use AI tools to create more content.” That may produce speed, but it does not necessarily create quality, coherence or sustainability.
A systemic response would redesign both architecture and essence. The architecture might include: a content calendar that links themes, audiences, channels and deadlines; a source repository containing approved stories, brand language, examples and visual assets; a workflow that moves content from idea to draft, review, approval, scheduling and post-publication learning; and feedback loops that show which content creates trust, conversation, conversion or community.
The essence would include: a shared belief that content is not a task factory but a learning engine, curiosity about what the audience is actually responding to and reflective practices anchored in a psychologically safe operating environment. In this example, AI tools may be useful, but they are not the innovation by themselves. They become innovative only when embedded in a system that improves judgement, flow, quality, speed and learning. Without architecture, the studio becomes chaotic. Without essence, it becomes mechanical.
Build Capability, Not Dependency
Many innovation programmes fail because they depend too heavily on a central team. The innovation office becomes the owner of innovation while everyone else remains a participant or consumer.
A sustainable culture requires distributed capability. People closest to the work must be able to diagnose problems, spot patterns, test improvements and contribute to system redesign. This means leaders should build capability and see interdependencies via feedback loops from users.
This matters because leaders often overinvest in the technical solution and underinvest in acceptance. They assume that if the solution is good, people will adopt it. In reality, people adopt when the change makes sense, feels usable, fits their context and is reinforced by the system around them.
In the content studio example, a new workflow will fail if creators see it as administrative control. It will succeed if they experience it as a way to reduce rework, protect quality, improve scheduling and make good ideas reusable. Acceptance is not communication after design. Acceptance must be designed into the system from the beginning.
That shift changes the work of leadership. Leaders stop treating innovation as a special event and start treating it as a management discipline. They clarify purpose, design architecture, cultivate essence, build capability, run learning loops and remove friction from adoption.
Innovation is not a lightning bolt. It is a learning system. Culture is what happens when that system is internalised and operationalised consistently, so people believe: “This is how we improve things here.”
by Thomas Lim | Jul 24, 2026
Innovation shouldn’t be a one-off project. It should be how your organisation learns, adapts and wins over time. Treating innovation as a repeatable capability, not a special project or a heroic individual changes how you design work, reward people and run experiments. The payoff is an organisation that continually sees opportunities early and turns small bets into scalable advantage.
Why Systems Thinking Changes The Game
Too often we chase bright ideas and ignore the plumbing that makes them stick. Systems thinking forces you to look past one-off events and see the patterns, structures and beliefs that produce them. Instead of asking “Why didn’t that product launch work?”, you ask “What ongoing processes, incentives and mental models are shaping what we try and what we ignore?” That shift reveals leverage points where modest changes produce big, durable results.
Three Things That Need To Fit Together
Mindset, people and structure are interdependent. Mindset shapes what problems people notice and which risks they’ll take. People bring the skills and judgement to test ideas. Structure — roles, processes, incentives and tools — channels resources and turns ad hoc learning into repeatable practice. If any of these are out of sync, progress stalls: curious teams without decision rights can’t scale, and clever systems without a learning culture become checkbox exercises.
See Beneath The Surface With Simple Models
The iceberg metaphor helps: surface events are symptoms, patterns show trends, systemic structures explain why those patterns persist, and mental models reveal underlying beliefs. Causal-loop thinking adds another layer: mapping reinforcing and balancing feedback shows how investments, habits and incentives interact over time. These aren’t academic toys — they’re diagnostic tools that help you avoid knee-jerk fixes and find sustainable interventions.
Make Constraints Work For You
Constraints often force smarter design. Tight requirements — on cost, speed or distribution — can push teams to combine solutions that solve multiple problems at once. Rather than seeing constraints as barriers, treat them as design parameters that compel elegant, practical solutions. When teams embrace limits, creativity concentrates where it matters.
Build A Learning Loop That Actually Scales
Effective innovation lives in two loops: an inner loop that changes people, and an outer loop that changes the organisation.
The inner loop is how individuals learn. They notice patterns, test small ideas, get feedback and integrate what works. This cycle builds new skills and changes beliefs — people become more comfortable experimenting because they see results and get coaching.
The outer loop operationalises those learning moments. It creates the architecture: guiding ideas, clear processes for idea intake and sprints, roles like coaches and champions, and infrastructure for knowledge capture and reuse. The outer loop makes sure local experiments become shared organisational practice.
Psychological Safety Is A Business Requirement
Teams that feel safe to try, fail and report honestly learn faster. When people fear blame, they hide mistakes and stall progress. Rewarding learning such as documenting hypotheses, sharing failed experiments and making small, fast bets, signals that the company values discovery over cover-ups. Margaret Heffernan has argued that organisations need “more freedom to invent and experiment” than they think; that’s not a feel-good slogan, it’s a practical hedge against uncertainty.
Traditional KPIs Can Kill Curiosity
If people are only measured on efficiency or short-term targets, they’ll avoid risk. Instead, add learning-oriented metrics: number of experiments run, time to validated learning, reuse of documented insights, and percentage of ideas that were tested and then adopted. Pair those with storytelling: short case summaries of what was tried, what was learned and what changed.
Fix The Incentives And Governance
Structure can enable or suppress innovation. Clear strategic intent, decentralised decision rights and learning-friendly incentives let teams move. Misaligned KPIs, top-down gatekeeping and reward systems that prize near-term predictability will strangle new ideas. Look at the real incentives — not the org chart — to see where behaviour is being shaped.
Stop Treating Innovation As A Department
Innovation isn’t a department you can box and hand off. It’s a capability embedded across functions. That means leaders must provide a guiding idea — a clear purpose that orients experiments toward value. From there, teams run small tests that feed a shared knowledge base. Over time, the company develops muscle memory: the default way to tackle problems is to sense, test and adapt.
Mind the human voices that derail progress Internal voices — judgement, cynicism and fear — are the invisible brakes. Practices that help teams open their minds, hearts and will (borrowing from Otto Scharmer’s idea) reduce those barriers. Simple habits help: pause before critical meetings to surface assumptions, ask “what surprised us this week?” and create fast, low-cost prototyping rules so people can try things without fear of catastrophic failure.
Use tools and infrastructure to amplify, not replace, judgment
Digital tools, AI and automation can speed learning, but they shouldn’t replace human judgement. The right infrastructure makes it easy to capture experiments, track approvals, and reuse validated knowledge. Think single source of truth with version history, simple experiment templates, and lightweight approval gates. Tools should reduce friction, not add bureaucratic steps.
Practical First Moves You Can Take
Start with a guiding question that everyone understands. Encourage a few small experiments that are easy to run and easy to learn from. Make it safe to share results, especially failures. Document what you learn in a searchable place. Set one or two learning metrics, appoint a few champion roles, and review progress with a simple loop: sense, test, reflect, scale. Small, early wins build confidence and create the momentum you need to change habits.
Building innovation capability takes time. It’s not a silver-bullet program; it’s an ongoing investment in how your organisation learns. But when curiosity, structure and incentives align, innovation becomes routine rather than heroic. You end up with an organisation that sees change early, tests smartly, and scales what works — prepared for whatever comes next.
If you are interested in learning more about building innovation as an organisation capability, check out SIM Academy’s 1-day course on Systems Thinking for Innovation & Change.
by Thomas Lim | Jul 6, 2026
This article is originally published on Forbes on 2 July 2026 []
Venture building has become faster than ever. A team can now use generative AI to scan a market, map competitors, draft customer personas, sharpen a pitch and produce plausible business models in a fraction of the time it once took. By many measures, this looks like progress. Ideas move quickly. Early narratives become polished. Investor materials look sharper.
And yet something does not add up. Many ventures still struggle to move from technical promise to market adoption. The issue is not a lack of effort. It is that many venture teams are solving the wrong level of problem. They optimise the technology while underestimating the system that determines whether the venture can scale.
The Comfort Zone Of The Product
Most venture teams begin where their confidence is strongest: the technology. This is understandable. The technology is often what gives birth to the venture. It is also where founders have deep expertise. But here lies the trap: Technical improvement is not the same as venture readiness.
Take a science and engineering startup in Asia working on no-code robotics automation, and the visible problem seemed straightforward: Make robots easier to program and deploy. But the deeper issue was more complex. Industrial customers already had proprietary robotics platforms, software ecosystems and operational routines. Each customer environment was different. Integration was not an afterthought. It was the venture problem.
At first, the team considered using an open robotics operating standard. On paper, this seemed sensible. It offered an existing foundation and reduced development effort. But deeper scrutiny surfaced important constraints. Licensing obligations could limit commercial adoption. A general-purpose robotics platform carried overhead that was not optimised for robotic arms. Customer deployment across different platforms would still require serious adaptation.
The eventual move toward proprietary kinematics, motion planning and robotic frameworks was not merely a technical decision. It was a venture architecture decision. It changed the company’s ability to be agnostic across customer systems, differentiate in large corporate environments and reduce adoption friction. That is the first discipline of systems thinking in venture building: Move beyond the product and identify the system constraint.
The System You Are Actually Entering
Every venture enters a system that already has structures, habits, incentives and beliefs. Customers do not adopt in a vacuum. They adopt through workflows, procurement processes, trust thresholds, integration requirements, budget cycles and professional norms.
Systems thinking helps venture builders locate the intervention layer. Some ventures operate at the application layer, offering a specific tool or feature. Others operate at the workflow layer, changing how people work.
Misreading this layer is costly. A team may keep improving a tool when the real constraint is workflow adoption. It may raise money for sales expansion when the real need is evidence generation. It may frame itself as a product company when investors are really evaluating whether it can become a repeatable platform.
Why Feedback Loops Matter
Ventures do not scale in straight lines. They scale through feedback loops.
A positive loop can build momentum. More customer deployments generate more data. More data improves the software. Better software improves customer outcomes. Stronger outcomes build customer confidence. More confidence drives more adoption. This is the kind of loop that creates venture compounding.
But a venture can also trigger resistance loops. More deployments expose more variation in legacy systems. More variation increases integration burden. Integration burden slows implementation. Delays weaken customer confidence.
Take the case of a certain biomedical startup in ASEAN. Its technology involved advanced tissue models and microfluidics testing systems for safety and efficacy studies. A narrow product lens would focus on the quality of the laboratory platform. A systems lens reveals a larger challenge: The venture had to move from local product development toward global deployability.
That required work that was not glamorous but was essential. Product liability had to be addressed. Insurance had to be secured. Distribution partners had to be selected carefully. Checklists had to be refined. The team had to determine whether broad catalogue distributors were sufficient or whether country-level partners with industry knowledge were more suitable.
This is where adoption logic matters. A useful formula is Q x A = E, where Q is the quality of the solution, A is the acceptance by people and E is the effectiveness of the result. A technically strong product with weak acceptance will underperform. Mathematically, if quality is seven and acceptance is four, effectiveness is 28. Improving quality from seven to eight lifts the result to 32. But improving acceptance from four to five lifts it to 35. For high-quality ventures, the more powerful move may not be another unit of technical improvement. It may be one more unit of acceptance through trust, usability, evidence, workflow fit and stakeholder confidence.
In another phase, the biomedical team considered providing testing services before scaling product sales. At first glance, this could look like distraction. From a systems perspective, it may be the evidence loop required for adoption. Sometimes the route to scale is not to push harder on the product. It is to build the conditions that make the product adoptable.
From Better Products To Better Venture Architecture
Systems thinking changes how founders and venture builders think about funding.
Many funding asks are framed around activities: hire engineers, expand sales, build features, enter new markets. These may be necessary, but they are often incomplete. A stronger funding thesis explains which system constraint the capital is meant to shift.
The best venture teams can explain how funding will strengthen a reinforcing loop or weaken a balancing loop. They do not merely say they need capital to grow. They show how capital changes the conditions for growth.
This is where critical thinking and systems thinking must work together. Critical thinking identifies what must be true for the venture to succeed. Systems thinking shows how those assumptions sit inside a larger structure. Creative thinking reframes what the venture could become. So, even though AI makes venture building faster. Systems thinking makes it wiser.
by Thomas Lim | Jun 9, 2026
This article is originally published on Forbes on 8 June 2026 []
Leadership conversations tend to focus on strategy, execution and capability building. Yet the most powerful force shaping innovation outcomes—the leader’s internal dialogue—is rarely discussed.
When organisations attempt transformation, leaders often assume resistance is external. They point to culture, structure or capability gaps. In reality, the first barrier to innovation is internal. It shows up as subtle emotional reactions that distort how leaders think, act and engage others.
The Fiends & Hero framework offers a useful lens. It identifies three “fiendish voices” that emerge under pressure: judgment, fear and care. These voices are not flaws; they are natural responses to leadership vulnerability. But left unmanaged, they can quietly undermine innovation at every level.
1. Innovation fails when leaders lose openness of mind.
The first voice is judgment. It appears when leaders encounter ambiguity, new ideas or perspectives that challenge their experience. The emotional signals are familiar. Irritation. Frustration. A sense of “This will not work.” Over time, this erodes psychological safety and reduces the diversity of thought needed for innovation.
This is how innovation dies quietly. Not through resistance, but through early dismissal. The underlying pattern is simple: A need to be right collapses curiosity. When leaders prioritise correctness over exploration, they narrow the solution space before it has fully emerged. The result is incremental improvement instead of breakthrough change.
2. Innovation stalls when leaders lose openness of will.
The second voice is fear. It emerges in moments of uncertainty, high stakes or perceived risk. Leaders begin to ask different questions. What if this fails? What if this affects my credibility? What if we get it wrong?
The emotional state shifts. Anxiety rises. Doubt creeps in. This does not always look like hesitation. In many organisations, fear shows up as overanalysis, excessive governance or a demand for certainty before action. Teams wait for clarity that never fully arrives. Innovation pipelines stall because experimentation never begins.
The pattern here is equally clear: Perceived risk outweighs perceived capability. When leaders feel exposed, they either avoid action or attempt to control every variable. In both cases, movement stops. Innovation requires forward motion under uncertainty, and fear removes that capability.
3. Innovation slows when leaders lose openness of heart.
The third voice is care. Unlike judgment and fear, this one appears positive. It is driven by concern for people, relationships and impact. Leaders feel responsible for how decisions affect others. But this is where the distortion begins.
Care becomes over-care. Leaders hesitate to make difficult calls. They soften decisions to maintain harmony. They value consensus over clarity. Over time, accountability becomes diluted and execution slows. Transformation efforts lose momentum because leaders avoid the tension required to drive it. The pattern is subtle: Leaders carry emotional burden that should be shared. The result is stagnation disguised as alignment.
Out of sight, out of mind.
These three voices operate beneath awareness. They shape perception before logic is applied. They influence interpretation before data is analysed. They guide behaviour before decisions are made. This is why traditional transformation efforts often fall short.
Organisations invest heavily in strategy, frameworks and capability building. Yet they overlook the internal conditions required for those tools to work. Leaders may understand what to do, but their internal state determines whether they actually do it. This shift is critical. You cannot manage what you cannot see.
The real work of leadership is state management.
If fiendish voices distort leadership capability, then the solution is not more instruction. It is intervention at the level of state. This is where the following Hero Powers come in. Each Hero Power is designed to restore a specific capability that has been disrupted.
Power One
When judgment takes over, leaders lose openness of mind. Power One introduces calm, nonreactive awareness. It slows down automatic evaluation and creates space for observation.
Leaders begin to ask different questions. What am I not seeing? What else could be true? This shift restores clarity of perception. It allows multiple perspectives to surface before conclusions are drawn, and the quality of thinking improves.
Power Two
When fear dominates, leaders lose openness of will. Power Two does not eliminate fear. It contains it. By stabilising the emotional surge, leaders regain the ability to act despite uncertainty. They focus on the next viable step rather than the entire risk landscape.
This restores momentum. Small, deliberate actions replace paralysis. Experiments begin. Feedback loops activate. Innovation moves from concept to execution.
Power Three
When over-care takes hold, leaders lose openness of heart. Power Three reframes concern into shared purpose. Instead of carrying the emotional burden alone, leaders engage others in the journey.
Conversations shift from protection to ownership. Tough decisions are anchored in meaning, not avoided for comfort. People understand not just what needs to change but also why it matters. Commitment strengthens. Momentum becomes sustainable.
Innovation requires all three capabilities.
Most organisations fail not because they lack ideas but because they cannot sustain the conditions for innovation. Conditions like clarity of thinking, decisiveness of action and alignment may sound simple, but they are demanding. The goal is not perfection. It is awareness.
In high-stakes moments, this changes everything. Check in with yourself:
- If you feel irritation, check for judgment.
- If you feel hesitation, check for fear.
- If you feel burdened, check for over-care.
Then apply these interventions as appropriate:
1. Pause and observe before evaluating.
2. Take the next step without needing full certainty.
3. Engage others around a shared purpose.
These are not abstract concepts. They are practical shifts that reshape leadership behaviour in real time.
Unlock the power of courage.
Innovation is often treated as a structural or strategic challenge. In reality, it is a human one. Leaders do not fail because they lack intelligence or intent. They struggle because of unseen internal dynamics that shape their decisions under pressure.
The Fiends & Hero framework can help reframe leadership development by recognising and working with these fiendish voices. In doing so, leaders can unlock something far more powerful than capability: courage. And in a world defined by complexity and uncertainty, that may be the most important leadership capability of all.
