“Matt brings a multitude of technical experiences and diverse expertise to any project he works on. We've worked together on a few projects and he's continuously willing to support not only those at his level but work with less experienced associates to further develop talent across our organization. For someone with the amount of responsibility he has, I've always appreciated his openness to take time for discussion and his efforts to foster a collaborative team environment. Not to mention, he's a cool guy -- there's never a shortage of interesting stories from or about Matt Lavallee.”
Matt Lavallee
North Grafton, Massachusetts, United States
2K followers
500+ connections
2K followers
500+ connections
About
Technology Executive | AI Adoption Leader | Cloud Modernization & High‑Uptime Systems…
Activity
-
Change communications should not be treated as a one-and-done event. Keep employees informed at every step of the process — with clarity and…
Change communications should not be treated as a one-and-done event. Keep employees informed at every step of the process — with clarity and…
Liked by Matt Lavallee
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
-
-
-
-
-
-
-
Licenses & Certifications
-
-
-
-
Certified SAFe 5 Lean Portfolio Manager
Scaled Agile, Inc.
Issued ExpiresCredential ID 11968142-8336
Publications
-
Attunity RepliWeb PR
Attunity
See publicationPress release on improvements gained by streamlining SAAS application delivery
-
Computerworld Article
Computerworld, Inc.
See publicationDiscussion on the software licensing impact of high-core CPUs.
-
Guest Post: Windows Virtualization Blog
Microsoft, Inc.
See publicationGuest post to the Windows Virtualization Blog regarding our move to virtualization and the real gains in TCO and efficiency.
Languages
-
French
Elementary proficiency
Recommendations received
4 people have recommended Matt
Join now to viewOther similar profiles
Explore more posts
-
Rick H.
What finally made this click for me wasn't a new model. It was a system. A system where: Each task runs in a fresh context Project state lives in files, not chat Agents do work and then disappear Only verified outputs persist No sprint ceremonies. No Jira cosplay. No "AI as magic." Just structured execution that respects how models actually work. I walk through the exact loop—discuss → plan → execute → verify—and why it prevents context rot by design. If you build anything non-trivial with AI agents, this matters. 👉 How AI agents forget what they're building—and how to fix it https://lnkd.in/gFC5KjHu
-
Margeaux Salmon Spring
Where does #a11y fit in your tech stack? Accessibility is infrastructure. Period. I’ve spent years building and auditing systems against Section 508 and WCAG. The biggest problem I see isn’t technical, it’s organizational. Teams treat accessibility like remediation instead of what it is: a core architectural concern on the same level as security and performance. Over 96% of the top million homepages have detectable WCAG 2 failures. We have the specs. We have the tools. What we don’t have is engineering leadership culture that treats a contrast ratio violation with the same seriousness as a broken API endpoint. And y’all, the regulatory landscape is catching up. April 24, 2026: DOJ’s Title II rule mandates WCAG 2.1 AA for public entities serving 50K+ populations. Private sector isn’t exempt, WCAG 2.1 AA is now the de facto standard in Title III litigation, up 102%. And you’re legally responsible even when using third-party platforms. That vendor VPAT does not equal a compliance strategy. What I’ve learned shipping accessible systems at scale: 1. Shift left, hard. Accessibility belongs in your component library, design tokens, and PR checklists. This should be as non-negotiable as type safety for your codebase. 2. Automate the floor, not the ceiling. Automated tools alone can’t catch everything, you need both automated and manual assessment. We don’t ship apps without auth. Stop shipping digital product without accessibility. #a11y #WCAG #Section508
1 Comment -
Amit Pundeer
In large technology transformations, the most dangerous decision is often the one that looks “cleanest” on paper. I’ve seen teams rush toward full rewrites of legacy systems because the architecture feels messy, outdated, or hard to reason about. In practice, the safer question is rarely “What’s the best design?” It’s “What keeps options open if we’re wrong?” Incremental extraction, controlled reuse, and preserving operational continuity may look inelegant—but they dramatically reduce irreversible risk. Senior technology decisions aren’t about elegance. They’re about survivability under uncertainty
2 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content