Looking back at the last ten months, I am deeply grateful for my time at Network Coverage and for the people I had the opportunity to work with along the way. These months were filled with challenging projects, fast-moving client needs, difficult troubleshooting sessions, migration weekends, and the inevitable edge cases that only seem to appear during a production cutover.
What stands out most is not just the technical work, but the support, collaboration, and guidance from the great people around me. I learned from engineers, project managers, consultants, leaders, service desk teams, and peers who were willing to share knowledge, jump into problems, challenge assumptions, and help move work forward when things were easy and when they were not. Many of these lessons were shaped by that environment and by the people who helped me grow through it.
These are the ten lessons that stand out the most.
1. Migrations Are People Projects Disguised as Technology Projects
One of the biggest surprises of my consulting career has been discovering that technology is rarely the hardest part.
The challenging part is helping people navigate change.
Users are not worried about mailbox databases, Azure AD Connect, authentication protocols, or migration tooling. They care about whether they can send email, join meetings, access files, and continue doing their jobs.
The most successful migrations I participated in were the ones where communication was treated as a first-class deliverable alongside the technical implementation.
2. Every Environment Has a One Percent Edge Case
No matter how clean the architecture looks on paper, every environment has something unique.
- A legacy application.
- An undocumented dependency.
- A forgotten server.
- A certificate nobody remembers.
- A security control that interacts differently than expected.
The lesson is simple: never assume something will work because it worked somewhere else. Validate everything. Then validate it again.
3. Identity Is the Foundation of Modern IT
If I had to identify the single most important technology pillar today, it would be identity.
Modern security, collaboration, compliance, device management, and application access all ultimately depend on identity. When identity is designed correctly, everything else becomes easier. When identity is poorly designed, every project becomes more difficult.
The organizations that invested in strong identity governance consistently had smoother implementations and fewer operational problems.
4. Security and Productivity Are No Longer Opposing Forces
There was a time when security and usability often felt like competing priorities. That is becoming less true every year.
The most successful organizations are implementing security that users barely notice.
- Passwordless authentication.
- Conditional Access.
- Application protection.
- Modern device management.
- Identity governance.
When implemented correctly, these controls frequently improve user experience while simultaneously increasing security.
5. Automation Always Pays Dividends
The best work is often the work you never have to repeat.
Throughout the year, I found myself continuously asking: Can this be automated?
Whether through PowerShell, Power Automate, Intune, deployment tooling, provisioning processes, or operational workflows, automation consistently delivered value.
Every minute invested in automation eventually returns hours or days of operational savings. Sometimes much more.
6. Documentation Is an Engineering Deliverable
There is a tendency in IT to view documentation as something completed after the project. In reality, documentation is part of the project.
The best environments I encountered shared several characteristics:
- Accurate documentation.
- Clear ownership.
- Standardized processes.
- Defined recovery procedures.
- Updated architecture diagrams.
Good documentation reduces risk, accelerates troubleshooting, simplifies onboarding, and preserves institutional knowledge.
Future engineers will appreciate it more than you realize.
7. Cloud-First Does Not Mean Cloud-Only
A significant number of projects involved modernizing infrastructure while continuing to support business requirements that could not immediately move to the cloud.
The lesson was clear: practical architecture beats ideological architecture.
Sometimes cloud-native is the correct solution. Sometimes hybrid remains necessary. The goal should not be to force a particular technology choice. The goal should be solving the business problem effectively.
8. Compliance Is a Business Requirement, Not a Technical Feature
Many organizations initially approach compliance as an IT initiative. Over time it becomes clear that compliance is actually an organizational initiative.
Technology can support compliance. Technology cannot create compliance alone.
Successful compliance projects required collaboration across:
- Executive leadership.
- Security teams.
- Compliance personnel.
- Operations teams.
- End users.
- IT engineering.
The best outcomes occurred when organizations viewed compliance as a culture rather than a checklist.
9. The Simplest Solution Is Usually the Best Solution
As engineers, it is easy to become attracted to elegant architectures, advanced tooling, and complex solutions. The reality is that complexity has a cost.
Every additional component introduces:
- Maintenance overhead.
- Troubleshooting complexity.
- Training requirements.
- Failure scenarios.
The longer I work in consulting, the more I appreciate simplicity. The best solution is often not the most impressive one. It is the solution that meets requirements with the fewest moving parts.
10. Great Teams Solve Problems Faster Than Great Individuals
This may be the most important lesson of all.
Over the last ten months, I worked with project managers, security consultants, architects, engineers, service desk personnel, customer success managers, compliance specialists, and operational leaders.
Every major success was a team success. Every difficult challenge became easier because people collaborated. Every project benefited from perspectives that no single individual could provide alone.
Technology changes constantly. Products evolve. Platforms come and go. What consistently creates success is a team of talented people willing to help each other and work toward a common goal.
That is what I will remember most from my time in Infrastructure Project Services.
Final Thoughts
When I think about the last ten months, I do not immediately remember specific tickets, migration jobs, policy configurations, or project timelines.
I remember the lessons.
I remember the challenges we solved.
I remember the customers we helped.
And most importantly, I remember the people.
Technology will continue changing. The lessons learned, relationships built, and experiences shared will remain long after the projects themselves are complete.
To everyone who was part of this journey, thank you.
It has been an incredible ten months.