Every architect and senior engineer hits this wall eventually. You see a better way to do something — a framework, a platform, a pattern — and you''re convinced it''s right. But you don''t own the budget, the roadmap, or the teams you''d need to pull it off. So how do you get people to move?
I''ve encountered this myself, and I see plenty of others wrestling with it too. Honestly, my experience boils down to a handful of things that actually work.
1. Prove it''s viable — hands-on
Reading articles and drawing diagrams are necessary. They generate ideas and let you present them conceptually. But nothing beats a POC demo of the idea. Even taking an online class or lab gets you closer to understanding the real risks and trade-offs.
Last year I proposed a framework to get our enterprise data platform CCPA-compliant in a way that was auditable and easy to implement. I don''t think I could have sold security, governance, and my architect peers on a diagram alone. So I built the module and ran it against test data — pointed at exactly what would be affected and how.
Doing that opened up the conversation to other decision points that needed to be made. Decisions that would have surfaced much later if we''d started with a conceptual model and waited to flesh things out.
By the way, proving viability includes an assessment of risks and how they will be mitigated. YOu''re not likely to influence leadership toward an idea that puts the company at risk.
2. Involve people early
Especially the people who own or are responsible for areas you don''t. Explain what you''re trying to do. Show them a high-level diagram. Let them poke holes in it. Respect their expertise — and when they make suggestions, genuinely consider that they might be right. Consider changing your design to address their concerns. Let them own a piece of it. Make them part of it, and they''re far more likely to want it to succeed.
This has come up many times in my career. One example: I wanted to leverage event-driven functions to make batch pipelines seamless, but the platform team didn''t have a repeatable template to provision functions, and they had issues with my design. So I changed it. At that point they built the template. We came out of that initiative with a lot more respect for each other.
3. Break proposals into phases
It''s much easier to convince leaders, executives, or seniors to agree on step 1 first. The low-hanging fruit — easiest effort for maximum ROI, minimum risk, or just whatever is pragmatic given current budget, resources, conflicting priorities, and tech debt.
If you do it right, phase 2 is an extension of phase 1, not an entirely new mental setup. Just avoid the trap of never actually getting to phase 2.
And if the timeline itself is what you''re trying to influence, frame why you need this now and not later. A real competitive advantage is the strongest case, but process improvement or cost control can be rationalized too — you just have to put in the effort to make that connection clear.
4. You don''t need to convince everyone at once
Gravitate toward the early adopters. Let them help you get the bugs out. The people who are more reluctant to change will come around eventually, if it truly is an enterprise initiative worth adopting.
I once built a platform that collected high-volume financial transaction data from divisions all over the globe — Germany, Mexico, the US, China. It was well governed, tying in the financial leaders, owners, and stewards from each division. But some of the salespeople still clung to their green bar reports. I''d told them early that changes to the analytical platform were coming, and they still trusted their printouts. I think they saw no reason to trust my influence until I could prove a value-add their reports didn''t have. Which leads right into the next point.
5. Earn trust by creating value
To influence change, prove you can add value — ideally before the transformational proposal, with a track record already behind you. If you need to close that gap, just ask leadership or your seniors what the problems are. Solve those first, before pitching your own innovative ideas. Then you''ve earned some runway.
6. Tie it to company goals and values
The influence comes off as an easier sell when you frame it in the context of a business goal or value. That''s usually a relatively short list, so it shouldn''t be hard to see which points your idea maps to. But the articulation of how it maps has to be clear.
It''s also possible that what you''re trying to influence is the goal or value itself — to better follow cultural dynamics, market shifts, or technology trends. If your rationale is sound, that may be even more worth pursuing, because it could be a genuine differentiator for your company.
A final thought
You''re not going to influence everyone toward your ideas every time. One of the special things about team and leadership dynamics is that there are always different points of view — and neither side is necessarily wrong.
I''d argue the best business structures don''t tighten any single objective all the way for the win. It''s the balance between competing objectives — teams and points of view regulating each other — that makes for a sustainable business.
0 Comments
Leave a Comment