Tuesday, November 10, 2026

Enterprise Network Modernization, Part 2: Where to Find Evidence That Isn't Just Slides

In Part 1 I argued for drawing your own map before buying anything. In short: the traffic lives in four domains (data center, campus and branch, WAN and secure access, multi-cloud and hybrid). Three planes govern it (operations and intelligence, security and trust, consumption and sourcing). A physical foundation sits under both. That makes 24 topics, each with exactly one home, decided by who owns the buying decision.

This part is about the question that bothers me even more: once the map is on the wall, where do you get the evidence to decide anything?

The conversation usually jumps straight to "so what do the analysts say?", and that quickly shrinks to looking at the top right corner of a chart. I understand the instinct. It is also how a lot of expensive decisions get made.

Not all evidence is equal

Roughly, from weakest to strongest in terms of relevance to your environment:

  1. Vendor material.
  2. Analyst reports.
  3. Peer conversations and references.
  4. Independent or lab testing.
  5. Your own data and your own proof of concept.

Breadth runs the opposite way. Analysts see the whole market and your data sees only you. So you need both, and you need to know which question each one can answer. Analysts can tell you where the market is heading and who the players are. They cannot tell you whether it fits your network.

Reading analyst output without being fooled

A few habits that have saved me time.

Read the text, not just the picture. The quadrant or the wave is a summary of a long document, and the interesting parts are usually the strengths, cautions and inclusion criteria. Check the date and the scope. A vendor can be a "Leader" in a market defined in a way that has nothing to do with what you want to buy. Remember what the chart does not measure: your fit. And remember who often pays for the copy you are reading. A lot of full reports are paywalled, and what is public is frequently a vendor's reprint or press release. I treat a press release as what it is.

Different firms also do different jobs. Gartner, IDC and Forrester are strongest at defining categories and comparing vendors across them, and they give you breadth. Gigamon, KuppingerCole, Frost and Sullivan and similar firms often go narrower and deeper into features and approach. I find it useful to ask how deep any piece of analysis actually goes. Roughly: does it stop at logos, at checkboxes, at features, at approach, at architecture, or does it get to what the architecture means for you? Most public material stops somewhere around the third step. The value is in the last two, and that is where your own architects and your field experience have to fill in.

And label forecasts as forecasts. Take a line like Gartner's earlier prediction, as reported in the trade press, that by 2026 sixty percent of new SD-WAN purchases would be part of a single-vendor SASE offering. That is a forecast, made at a point in time, by someone with a view. Fine to read, risky to quote as adoption. Always ask who counted, and when.

What the coverage looks like on my own map

I tagged each of the 24 topics with whatever named public analyst evaluation I could find. The pattern was clear enough to be useful. Security and operations are well covered. There is a Gartner quadrant for hybrid mesh firewall (September 2026), Forrester Waves covering SASE and zero trust platforms (both Q3 2025) and network analysis and visibility (Q4 2025), and a Gigamon Radar for network observability (version 6, April 2026). Wireless LAN has both a Gartner wired and wireless LAN quadrant (May 2026) and an IDC MarketScape (2025). Carrier WAN services and managed services have Gartner quadrants too, for global WAN services (March 2026) and managed network services (April 2026).

At the edges it thins out quickly. For edge or micro-DC, IoT and OT networking, optical transport, cloud-native networking, cloud interconnect, service mesh overlays and passive infrastructure, I did not find a named public evaluation I could point to. To be fair, I may have missed some, and paywalled research may cover more than I can see.

That is not a verdict on those topics. Often it is the opposite, because these tend to be the early ones. It just means you should lean harder on field evidence and your own testing, and be more careful about confidence. A gap in analyst coverage is a flag, not a conclusion.

The routine I follow: gather, churn, synthesize

It is boring, and it works.

Gather from three lanes. Market definers for the big picture. Specialists for depth. Then the field: lessons learned, post-mortems, honest conversations with people who have done it, plus your own research. Do not skip the third lane, because it is the only one that is about reality instead of positioning.

Churn is the unglamorous middle. Put everything on the map, topic by topic. Date-stamp each finding. Mark each number as forecast or observed. Cross-check anything important against a second independent source before believing it. Write down where sources disagree and where there is nothing at all. This is where most people stop caring, and it is where most of the value is.

Synthesize into one page per topic. Market context. Adoption, dated and labelled. Considerations. Challenges. The vendor landscape, if you want to show one, on axes you define yourself and disclose, rather than something that looks like somebody else's chart. And a recommendation. Then add one more line: where does practice differ from what the analysts say? That is the field check, and it is often the most interesting sentence on the page.

Your own data is the best evidence you have

The good news is that you probably already own more of it than you think.


None of that comes from a slide. All of it is more relevant to your decision than any quadrant.

The field matters just as much, so write down your own lessons learned while they are fresh, and ask peers what went wrong, not only what went well. When you talk to vendors, ask for the reference that did not go well. I wrote some questions along those lines years ago for self-driving networks (Few Questions You Should Ask Your fav Self-Driving Networks Vendor). The technology names have changed, the questions mostly have not.

Rate the evidence, not just the technology

This is a small habit with a big effect. For every topic, rate two things separately. How attractive is the technology for us? And how confident are we in the evidence behind that? A topic can be attractive and poorly evidenced, which usually calls for a small, reversible experiment and not a big commitment. A topic can be well evidenced and unattractive, which usually means leave it alone. Keeping the two scores apart stops a persuasive demo from doing both jobs at once.

A quick worked example: quantum-safe

Take one topic and run it through the routine, quickly.

Market context: Gartner's 2026 trends for enterprise networking name quantum-safe networks, agentic NetOps and network sovereignty among the themes to watch, and its 2026 Hype Cycle points at regulatory, sovereignty and quantum pressures on network security. So the direction is not in doubt.

Adoption: here I would be careful. What I can find publicly is mostly forecasts and vendor announcements, not measured adoption. I would mark it forecast and leave it there.

Considerations: some data has a long shelf life, and some of your equipment has a longer life than your planning cycle. Whether your vendors support what comes next in firmware matters more than what they say on a roadmap slide.

Challenges: before you can protect anything, you need to know where cryptography is used, and in most organizations nobody has a complete answer.

Own data: the cryptography inventory from the table above. Field: ask peers who have started one how long it took and what surprised them.

Recommendation, and this is a judgement call: start with the inventory, and put crypto agility questions into your next network RFPs. Do not start a rip-and-replace Programme on forecasts. Confidence: reasonable on direction, low on timing.

Notice what happened there. Nobody bought anything, and we now know what to do next.

Where I would start on Monday

Draw your own version of the map, and argue about it until the boxes stop moving. Pick four to six topics, not twenty-four. For each one, find out what the market says, find out what your own data says, and write the two side by side. Mark everything as forecast or observed, with a date. Rate the evidence separately from the technology. And before any budget gets approved, ask the person presenting to show you where it failed for someone else.

None of this is clever. That is rather the point. Stay grounded and keep it real.

HTH...

A Tech Artist 🎨

Sources and further reading

Full reports are largely paywalled. What follows is what I could verify publicly, by title and date, including vendor reprints and press coverage where that was all that was visible.

Posted by at
Labels: , , , ,

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)