Scott Brinker has a vivid way to describe the pressure leaders feel when technology advances faster than their organizations can adapt: one foot is on the dock, the other on a departing ferry. The gap keeps widening, and trying harder does not make the position more comfortable.
His observation, known as Martec's Law, contrasts rapid technological change with the much slower pace of organizational change. Brinker is careful about the word “law.” He presents it as an empirical observation, not a formula that predicts exactly how every organization will behave.
In this conversation with Dr. Christian Mühlroth, the HubSpot platform ecosystem leader explores what managers can actually do about that tension. His answer combines deliberate choices, more adaptable ways of working and a willingness to benefit from innovation outside the company. It also leaves room for a reassuring thought: you do not need the theoretically perfect technology stack to run a successful business.
Brinker's first recommendation is to be selective. More change is happening than any organization can absorb effectively. Trying to respond to all of it creates a familiar failure: many initiatives begin, but none receives enough attention to work well.
Instead, examine which developments are most relevant to the business and its customers. Pick one or two and focus on getting them right. That requires saying no to interesting possibilities, including some that competitors or commentators are enthusiastically discussing.
The second recommendation is to improve the organization's ability to adapt. Brinker points to technical architectures that can evolve, agile management practices, and investment in training. None removes the difficulty of change. Together, they can make it easier to respond without rebuilding everything each time.
For an R&D portfolio, the implication is to treat organizational capacity as a real constraint. An attractive technology does not become a good investment simply because it is available. The team also needs the attention, skills and operating conditions to put it to use.
Brinker's experience mapping the marketing technology landscape gives this argument a memorable human dimension. What began as a map of a few hundred products expanded into thousands. No single company could plausibly contain all that experimentation.
He would show the map to executives at conferences and ask what they saw. Many treated its complexity as a sales argument: customers could avoid the mess by buying everything from one provider.
When Brinker discussed joining HubSpot with Brian Halligan, he brought the same question. Halligan saw opportunity. Rather than fight the expanding landscape, why not find a way to work with it?
Brinker's reaction was immediate:
“Okay, you had me at hello.”
A platform ecosystem makes a different allocation of innovation possible. Many companies can try different approaches in parallel, while a shared platform helps customers combine the products that suit them. The platform's job includes making those connections usable. Customers should not have to assemble everything themselves with what Brinker describes as duct tape and rubber bands.
A large market creates choice, but no buyer can evaluate every option. Brinker introduces the idea of satisficing: finding a combination that meets the need rather than endlessly searching for a theoretical optimum.
The relevant test is whether the tools support the strategy, customer experience and business the organization wants to build, at an acceptable cost. If they do, the existence of another possible combination is not automatically a reason to start again.
That changes the next question from what else the company should buy to how well it uses what it already has. Brinker sees complexity inside existing technology stacks as a substantial obstacle. Capabilities can be available without being easy for people to find or apply.
He is interested in AI interfaces partly for that reason. A user might describe a report in ordinary language rather than learn every menu and configuration. The system could produce the report and show the settings it used, allowing the person to inspect and adjust the result. He presents that as a promising possibility, not a guarantee that complexity has disappeared.
Brinker does not assume that AI agents or no-code tools will replace established business software wholesale. Recreating a sophisticated core system may be technically possible without being a sensible use of a company's resources.
He instead describes platforms supplying core capabilities, governance and systems of record. Teams can then build workflows and customer experiences around those foundations, tailored to the needs of their particular business.
This is a practical distinction for innovation leaders: identify where customization creates an advantage and where a shared foundation is sufficient. Building something yourself is not evidence of differentiation. The benefit has to come from what the resulting capability enables.
Brinker is similarly cautious about predicting one universal commercial model. Seat-based, usage-based and outcome-based pricing may coexist because they serve different needs.
The conversation eventually turns from software capability to human capability. If AI takes over tasks, do people gain room for more valuable work, or lose skills they still need?
Brinker asks where the recovered time and attention will go. Automation can be valuable when people can redirect that capacity productively. That transition will vary between roles and organizations; it will not happen effortlessly for everyone.
His own unfinished task is more ordinary: unplugging from screens more often. Even someone who spends his career interpreting technological change needs space to reflect. For leaders deciding what to adopt next, that is a useful place to begin: make room to choose before committing the team to more change.