Outcomes, Process, and Technology always come second. People. That’s where we should focus our efforts, and everything else will fall in place.
Keep it Simple.
The skills I’ve learned from over 18 years of experience in cybersecurity, technology, and leadership carries over more than one would think to my time outdoors and in search and rescue and EMS. Incident management, while the stakes vary, is very similar regardless of where its deployed. The primary purpose of this blog/website is to talk about what I’ve learned during my primary career. But I am splitting it out to also talk about what I’m learning as I’ve begun to officially put to use my experience outdoors. Check out the Search and Rescue portion for the details outside of technology: Blog - Search and Rescue — alaniz.io
Business Enablement.
If the programs and processes we put in place don’t enable business, then we have failed. I preach customer success to all of my teams no matter where in an organization they sit. We have to consider the customer first. What do they need? What do they want? Do they understand the services we provide? Can they engage us easily? Can they consume our deliverables quickly?
Perspective.
One of the core tenants of any team I put together is understanding three perspectives. If we approach something with only one, then we will leave too much on the table to offer value. We must consider the Business Perspective. What does the business need from this? We must consider the Technology perspective. How and where does technology fit? And we must consider the Information Perspective. What does the information flow look like. These three things are essential to delivering technology services successfully.
Some of my thoughts.
You can ask anyone who has worked with me. You don’t have to guess what I am thinking. Understanding the nuances of the programs we build is key. I build programs and I build teams. Here is some insight into the technical philosophies I implement.