I keep hearing the same concern from foresight, strategy, and innovation leaders: expectations go up, headcount does not.
Meanwhile, the world does not exactly slow down to help. New technologies emerge, regulation shifts, competitors move, customer behavior changes, and your team is somehow supposed to keep track of all of it, make sense of it, and turn it into something leadership can actually use.
That is a big ask for any team.
In many organizations, the response has been predictable. Build a scanning network. Add more contributors. Subscribe to more sources. Create better templates. Hold more review meetings. Produce another trend radar. Try to keep the whole thing moving through sheer commitment.
I understand why. I have seen that model up close many times, and for a while it can work well.
Until it doesn’t.
At a certain point, the issue is no longer effort or competence. It is scale. The system starts asking too much from people and too little from the infrastructure around them. And that is when foresight teams easily get consumed by growing workloads, while strategic influence remains frustratingly inconsistent.
If that sounds uncomfortably familiar, you are not alone.
When a solid foresight process still struggles
Let me tell you about Celine.
This is a composite story based on real organizations I have worked with. The details vary, but the pattern is very real.
A few years ago, Celine, an innovation manager, was asked to build a more systematic trend monitoring and horizon scanning capability to support innovation work across the organization. She approached it seriously. She chose sensible methods, defined responsibilities, and set up a continuous scanning practice instead of another one-off project. She also built a distributed scouting network, around 80 people across the organization contributing observations and signals alongside a smaller group responsible for coordinating specific technology and trend domains.
In other words, she did the hard part well.
The practice became structured. Technology and trend radars started taking shape. Internal stakeholders had a way to access future-oriented insights instead of relying on scattered reports and individual hunches. For many teams, that would already be a meaningful step forward.
But then reality did what reality does.
The number of topics to cover grew. The amount of incoming information exploded. The team could not be true experts in every relevant domain. Some internal stakeholders were engaged, others less so. Budget cuts arrived, because of course they did. Suddenly the same organization that wanted broader, deeper, faster futures intelligence was providing fewer resources to produce it.
That is the part of the story that tends to get skipped in conference slides. The setup can look sensible and still become fragile under pressure.
Why many strategic foresight teams hit a wall
Most mature foresight teams are not failing because they lack intelligence, discipline, or methodology. They hit a wall because too much of the workflow remains stubbornly manual.
Some of that manual work is valuable. Interpretation should remain human. Judgment should remain human. Strategic discussion should certainly remain human.
But a surprising share of the work that fills calendars is mechanical rather than strategic:
-
scanning large volumes of sources
-
filtering weak signals from noise
-
grouping related developments
-
drafting initial summaries
-
formatting outputs for different audiences
-
rebuilding essentially the same analysis in slightly different forms
That kind of work is necessary, but it is also exactly where scale becomes painful.
You can ask more people to help. You can ask existing people to work faster. You can add more process. Yet after a while, none of that changes the underlying economics of the work. The team is still trying to process an expanding world through a largely manual system.
And that has consequences as comes to response times, and as comes to the depth of research.
Most importantly: the people doing the foresight work end up spending less time with the questions that actually determine impact. Which uncertainties matter most? Which assumptions behind our strategy are becoming shaky? Which emerging risks deserve monitoring now, before they become tomorrow’s crisis? Which opportunity spaces deserve more serious exploration?
After all, what is the value of better scanning if it does not improve a single important decision?
What changed for Celine
Celine did not solve her problem by rebuilding the same model with fewer people. She changed the operating logic.
Her team adopted FIBRES Foresight Agents to support the most time-intensive parts of horizon scanning and futures intelligence work. The immediate gain was not flashy. It was practical. The team could automate large parts of scanning, organize findings faster, generate first drafts of trends, summaries, and scenarios, and work from a much stronger starting point than before.
That shift had a surprisingly human effect.
Instead of stretching a shrinking team across an ever-growing number of research fields, she could focus the people on the parts where people add the most value. Aligning with stakeholders. Framing the right research questions. Challenging interpretations. Connecting signals to strategic choices. Facilitating new decision-making to actually create an impact.
Earlier, the organization relied on a much broader part-time contributor network to support scanning. Today, a smaller group, around six to eight responsible people, can work across many more topics than before. What used to take months to get moving can now produce a first structured output in roughly an hour. What used to depend on manually reviewing hundreds of sources can now draw from a much larger global source base with far better coverage.
Those are meaningful gains. But the more important change is where time goes.
The team spends less time hunting for input and more time building understanding.
That is where strategic foresight starts becoming more useful to the rest of the organization.
What AI horizon scanning changes in practice
There is still a lot of confusion around AI in foresight. Some people expect magic. Others expect a black box. Neither expectation is particularly helpful.
In practice, what matters is far more concrete.
A good AI-supported foresight workflow can help a team:
-
prepare a research plan around a chosen topic
-
identify relevant topics and search angles
-
scan a broad pool of quality-controlled sources
-
detect patterns across weak signals and developments
-
suggest initial clustering, themes, and connections
-
draft trend descriptions, implications, source summaries, and scenarios
-
create great first versions of a trend radar or technology radar
That does not mean the work is finished. But it does mean the team is no longer starting from a blank page or from a pile of bookmarks and browser tabs.
That difference matters.
In our own case, I recently explored the future of B2B SaaS as a research topic. I started with the topic itself, then worked with the system to shape a research plan, define the evaluation logic, and expand the search angles. From there, the agentic workflow explored a large global source pool, gathered thousands of relevant articles, and synthesized them into a structured set of trends and phenomena within about 30 minutes.
Useful? Very.
Final? Hardly.
The point of that workflow is not to bypass expert judgment. It is to give experts a much better place to begin. You can rewrite, challenge, refine, merge, split, discuss, and contextualize the findings with your colleagues. You can connect them to your strategy, your innovation portfolio, your risk monitoring, your R&D agenda. You can trace insights back to the source material instead of hoping everyone will trust the summary because it arrived in a polished slide deck.
That last part matters more than many people realize. Mature organizations do not need more polished speculation. They need clarity they can defend.
From scattered signals to shared intelligence
One of the most frustrating things in large organizations is how much futures intelligence never becomes shared intelligence.
Someone in R&D notices a technical shift. Someone in market intelligence sees a competitor move. Someone in regulatory affairs spots an early policy signal. Someone in strategy has concerns about assumptions that no longer feel stable. Each observation is useful on its own, but unless there is a structured way to collect, compare, connect, and discuss them, they remain isolated fragments.
This is where a proper foresight platform earns its keep.
Not because it stores information more neatly, though that helps. And not because it can generate a prettier trend radar, though that can help too. Its real value is that it gives the organization a living environment for futures intelligence. Signals, trends, technologies, summaries, and scenarios can be built, challenged, linked, and reused over time instead of disappearing into project folders and forgotten presentations.
That continuity changes the quality of the conversation.
A trend radar stops being a one-time communication asset and becomes something people can return to, update, and use. A weak signal is no longer a loose note from one contributor but part of a growing evidence base. A futures intelligence process becomes easier to embed into annual strategy, innovation portfolio reviews, risk discussions, and technology scouting because the material does not need to be recreated from scratch every time.
This is one reason I believe the best organizations are moving away from static reports and toward living foresight systems. The latter simply fit the reality of decision-making better.
Why this matters beyond the foresight team
The benefits of a stronger foresight workflow do not stop with the foresight team.
For strategy leaders, this means a better basis for discussing long-term assumptions and testing strategic options before committing too heavily to them.
For innovation teams, it means earlier visibility into emerging needs, technologies, and opportunity spaces, without relying only on hype cycles or isolated scouting efforts.
For risk and resilience teams, it means a more forward-looking capability to monitor weak signals and emerging issues before they become obvious enough to land on every dashboard.
For R&D leaders, it means a more structured way to track developments across scientific, technological, market, and regulatory domains, rather than looking at each in isolation.
And for executives who mainly consume these outputs, it means something refreshingly simple: clearer insight, better traceability, and fewer conversations where everyone politely pretends that a static slide deck represents a living picture of change.
There is also a cultural effect. When the underlying system becomes easier to use, foresight stops feeling like a specialist ritual and starts becoming more participatory. People can contribute without needing to become full-time futurists. That is often how futures literacy actually grows inside an organization, not through abstract evangelizing, but through practical involvement.
The organizations pulling ahead are redesigning the work
I do not think the most important shift here is that AI can help with scanning. Useful as that is, it is only part of the story.
The bigger shift is that organizations finally have a chance to redesign how foresight work happens.
For years, many teams have been stuck with a trade-off that seemed unavoidable: either you keep the work rigorous and struggle to scale it, or you simplify it enough to scale and risk losing depth and credibility. That has been a painful trade-off, especially for in-house teams who need both.
Now there is another path available.
You can use AI to expand coverage, accelerate the repetitive parts, and surface patterns earlier. You can keep humans firmly responsible for interpretation, challenge, prioritization, and decision support. You can build a futures intelligence capability that compounds over time rather than resetting every quarter. You can give stakeholders access to something more useful than a PDF that was already aging the moment it was exported.
That is a meaningful operational shift. It also happens to be a strategic one.
Because in the end, the organizations that handle uncertainty best are rarely the ones with the most impressive trend vocabulary. They are the ones that notice change early enough, discuss it well enough, and act on it with enough confidence to matter.
A practical question worth asking now
If your team had a stronger starting point tomorrow, what would you do differently?
Would you cover more domains with the same people?
Would you spend more time with business units and decision-makers?
Would you build more robust trend radars, scenario work, or risk monitoring practices?
Would you finally have room to connect strategic foresight to actual choices instead of explaining, once again, why the team is still collecting input?
That is the question I would encourage you to sit with.
Every organization certainly does not need the same exact setup, but many teams have accepted unnecessary constraints for too long. They have become so used to the manual grind that they mistake it for rigor when it actually is friction.
And friction has a way of making smart teams look slower, narrower, and less influential than they really are.
The good news is that this can be changed.
If you want to see what that looks like in practice, from AI horizon scanning to collaborative trend radars and evidence-backed futures intelligence workflows, it is worth taking a closer look. The teams getting ahead are not waiting for calmer conditions. They are building the capability now, while the pressure is already real.
