RedCloud has been recognized as the Management Consulting Business of the Year (United States) at the Global 100 – 2026 awards, and we couldn’t be more proud of what this moment represents. It’s a celebration of the values we’ve carried since our early days in the Pacific Northwest and the trust clients place in us as they navigate modernization, security, and emerging technologies. As our global presence grows, we’re excited to continue strengthening our people‑first consulting model and delivering the practical guidance leaders rely on in fast‑moving environments. This award reflects the momentum behind RedCloud’s expansion across business and technology transformation, physical security, and data and AI enablement. We’re building a consulting model rooted in long‑term partnerships, measurable outcomes, and a belief that doing the right thing is the strongest foundation for growth.Read the full GPMG article.

Garrett Garcia leads Security System Design and Delivery across the Americas, guiding a team of TPMs who keep data center construction projects moving smoothly. He’s known for cutting through ambiguity, aligning teams, and keeping complex security work on track across dozens of sites. With experience in 15 countries and more than 300 data centers, he brings a practical, real‑world lens to every project. Outside of work, Garrett stays grounded through family life, road trips, karaoke nights, and a long‑running passion for RF and wireless security. He’s equal parts technical, curious, and down‑to‑earth. Get to know him better in his full 10‑minute feature. Describe your role and what you do in a nutshell. I am the North and South America Regional Lead for the Security System Design and Delivery team. In a nutshell, I lead the day-to-day operational work of a team of Security System Design and Delivery TPMs who manage active data center construction projects across the Americas. Our work focuses on data center security systems, including access control, CCTV, and perimeter security detection. My role is to help keep complex projects moving by aligning teams, removing blockers, managing priorities, and ensuring security system delivery remains coordinated across sites, vendors, and partner teams. What do you consider the most important skill for someone in your role, and why? The most important skill is the ability to turn ambiguity into execution. Data center construction and security systems delivery involve many moving parts: technical requirements, construction schedules, site conditions, vendors, partner teams, and regional differences. There is rarely a perfect amount of information, but the work still has to move forward. For me, the key is aligning people around the details, making decisions with the best information available, and keeping programs moving despite uncertainty. I try to stay grounded by sticking close to day-to-day details, because the facts behind how things get done are often covered in nuance. At the same time, “trust but verify” is important in this role. You have to build trust with people, but you also need enough discipline and follow-through to ensure the work is actually moving as everyone expects. What are you most proud of in your career so far? I am most proud of the scale of my data center security work and the perspective it has given me. Since moving into data center security in 2018, I have had the opportunity to work in 15 countries and visit more than 300 data centers. That kind of field experience changes how you think about security. You learn quickly that good design has to work in the real world, not just on paper. Every site has its own constraints, priorities, construction realities, and operational needs. I am proud to have built a career around helping teams deliver security systems in those complex environments, at a scale where consistency, adaptability, and follow-through really matter. How do you maintain a healthy work-life balance in your role? For me, work-life balance starts with being intentional about where my time and attention go. In a role with many meetings, shifting priorities, and a large team to manage, it’s easy for the day to become completely reactive. I try to stay focused on what actually needs my involvement, where I can help unblock the team, and where a better process can prevent the same problems from repeating. Outside of work, my family keeps me grounded. I grew up the oldest of 10 kids, so I had lots of practice with chaos, competing priorities, and people asking me where things were before I was even old enough to have a job. Now I’ve got three young kids of my own who make sure and remind me to take time and focus on life outside of work. What is a piece of obsolete technology you still have a soft spot for? I have a soft spot for vinyl records because they are true physical media. There is something that makes music seem more soulful when it’s played from a needle running through grooves of wax. Today, music is convenient, but I think you experience listening to an old record more intentionally. It takes a few minutes to set it up correctly and enjoy it, like using a French press to make coffee vs. pressing a button on a Keurig. What is one thing people do not know about you that they would be surprised to discover? People might be surprised to learn that I have a passionate interest in radio frequency technology and wireless security. That interest started a little over 20 years ago when I worked for Verizon installing fiber internet service. I would often run into interference from multiple wireless networks in the same area, so I started scanning for neighboring networks to make sure I was setting up wireless service on the cleanest available Wi-Fi channel. That curiosity eventually grew into a broader interest in RF as an attack surface, including Wi-Fi, Bluetooth, LR-WPANs, drone detection…I’ve gotten to use lots of cool spectrum analyzers! I was able to apply those interests early in my career, building and scaling a global Wireless Intrusion Detection & Response program across hundreds of data centers worldwide. A fun byproduct of that work was that I got to attend the DEFCON30 hacker convention, and the Wireless CTF team I competed with won the competition! What are you passionate about or enjoy outside of work? Outside of work, when I’m not just spending time with my family, I love singing karaoke in packed bars or doing pub trivia. In the summer, I really enjoy road trips with my kids because I’ve flown so much for work. Now, even stepping on a flight to Disneyland makes me feel like I’m clocking in, and I think taking the extra time to travel offers a great opportunity to create lasting memories for my family.

As organizations accelerate AI adoption, executive pressure to move faster while cutting costs is creating an unintended consequence: a growing pinch in the middle of the organization. This pressure is often described as a productivity issue, but that framing misses the point. What looks like slop is not laziness. It is the predictable outcome of asking high performers to do more with less in an environment where AI fundamentally changes how work is produced. This article clarifies what that slop really is, why it creates real organizational risk, and what leaders need to do next. The Productivity Paradox For most of modern work, our minds work faster than our hands. AI removes that constraint. Individuals can now generate strategies, papers, applications, and even systems almost instantly. At the individual level, the problem is easy to recognize. A long document produced by AI is not fully owned by the person who requested it, and its quality or accuracy cannot be taken for granted. At the organizational level, the same dynamic applies, but the consequences are much larger. When AI tools are turned on or piloted without the usual rigor around tool selection, business justification, usage clarity, or operational capacity, organizations begin producing work faster than they can validate, govern, or sustain. This is where slop appears. Not because people care less, but because production speed has outpaced organizational readiness. From Slop to Risk Unchecked AI adoption introduces compounding risk. Forward-looking organizations may already have, or soon will, thousands of AI agents operating simultaneously. Users can now generate applications for themselves, leading to rapid growth in loosely governed tools. At the same time, high performers who have succeeded under constraint assume they can do so again, even though the nature of the constraint has fundamentally changed. Without clear governance and some form of AI resource management (tokens), these dynamics create organizational slop at scale. Work exists, but it cannot be confidently trusted, maintained, or explained. Over time, this will erode credibility rather than create an advantage. It also introduces a longer‑term financial risk: token consumption becomes a black box, and future costs can spike without warning. The Leadership Constraint The hardest challenge for leaders is not technical. It is behavioral. In an environment that feels increasingly fast, the instinct is to move faster still. Run Faster! is all our brains hear. Often, the right response is the opposite. Slowing down does not mean resisting AI. It means reapplying discipline. That includes making conscious, informed decisions, establishing clear ownership and governance, integrating AI into real workflows, and ensuring the capacity to maintain, iterate, and scale what is built. These practices create reliable returns and protect organizational credibility, something AI alone cannot provide. A Warning Signal Leaders Should Not Ignore The tension between operational capacity and intellectual capacity is now a leading indicator of organizational risk. If individuals feel this mismatch in their daily work, it is almost certainly present at the enterprise level as well. When conversations about AI risk, current use, and future use are not coordinated and structured, organizations are effectively outsourcing judgment to systems they do not yet fully understand or control. AI does not fail organizations. Unexamined speed does. The path forward is full of intentional pauses that allow leaders to assess, decide, and build scalable capability. If your organization has not yet had a structured conversation about AI risk, governance, and long-term use, the signal is clear. Start that conversation now. This is how credibility and durable value are built, and how you protect the most important asset of your organization: critical thinking and the ability to generate genuine ideas. Catch up on the first two parts of the AI learning series.

AI‑assisted development unlocks extraordinary speed — but speed without discipline creates risk. The organizations that win in this new era aren’t the ones who adopt AI the fastest. They’re the ones who adopt it responsibly. This part of the series focuses on the realities: where AI falls short, what still requires human judgment, and what we’ve learned from building real solutions with clients. Where AI-Assisted Development Falls Short (For Now) Honest take from the trenches: AI is extraordinary at writing code and unreliable at almost everything around the code. Watch for: Scale. AI handles a function brilliantly, and a 200-file feature competently. It still struggles to reason about distributed systems, performance under load, and architectural decisions whose consequences play out months later. Infrastructure. Provisioning, networking, identity, data residency, the unsexy plumbing that makes software actually work in an enterprise, remains heavily human-led. Security. Generated code can introduce subtle vulnerabilities, SQL injection, XSS, leaked secrets, and compromised dependencies. AI is also a powerful tool for finding security issues, but unsupervised generation without a security review is a liability waiting to happen. Test quality. AI can write a lot of tests quickly. It’s much harder to get tests that meaningfully exercise edge cases, fail loudly when something real breaks, and don’t just pad coverage metrics. Support and operations. When something breaks at 2 a.m., the person paged needs to understand the system. Code they didn’t write and don’t understand is a runbook problem waiting to happen. Throwaway vs. production. Maybe the single most important distinction. A vibe-coded prototype is brilliant for validating an idea and dangerous if it slips into production unchecked. Knowing which is which is a discipline, not an instinct. The pattern is clear: AI compresses the building phase. The phases on either side, readiness and operations, are still mostly human work, and skipping them is how AI projects go sideways. What We’ve Built With AI-Assisted Development We don’t just talk about this, we live it. A few examples from our own bench: Coding Change Management Platform. A full change-request platform application, data model, analytics, and workflows built using AI coding agents alongside Power Platform Maker. The result: a scalable, user-friendly system delivered with significantly less developer time. This is agentic engineering in practice. Data Engineering Query Automation. Monthly and quarterly dataflow queries used to take weeks to update in response to revised metrics. We built an AI agent that interprets business rules and automatically updates queries. Development time dropped from weeks to hours, with fewer errors and faster adaptation when requirements shift. RedCloud Project Management Agent. An autonomous agent that emails consultants for status updates, interprets the responses, and updates the project management system on its own. Status collection went from hours to minutes, and project visibility went up not down. Self-Service Governance Agent. Governance, security, compliance, and privacy policies were scattered across teams, sites, and documents. We built an AI agent that consolidates the answers in one place. Adoption hit more than 50% of the organization, and the volume of governance questions flooding email and Teams dropped sharply. The throughline: AI didn’t replace the build; it changed the economics of building. The companies that thrive in this new era won’t be the ones who simply “add AI.” They’ll be the ones who redesign how they build — combining AI acceleration with human judgment, governance, and operational rigor. 2026 is the year organizations experiment. 2027 is the year the gap becomes obvious.

Sean Dettloff brings a builder’s mindset and a calm command of complexity to RedCloud’s growing Physical Security Practice. As the leader shaping this new capability, he’s focused on standing up an embedded team that supports a Fortune 500‑scale data center program—from early‑stage design to on‑the‑ground delivery of physical security systems. His work sits at the intersection of construction, compliance, and client partnership, ensuring every project meets rigorous standards while moving at hyperscale speed. In this edition of 10 Minutes With, Sean shares what energizes him about the role, how he approaches balance in a fast‑moving environment, and the experiences that shaped the way he leads. Describe your role and what you do in a nutshell. I’ve joined RedCloud to lead and support the development of our physical security practice area. At the moment, I’m focusing on building our embedded physical security design-and-delivery team that supports client data centers. We are in the early days of recruiting and developing a security practitioner team to support physical security design and the delivery of physical security hardware and systems in the data center environment. Much of our work supports new data center construction projects, but we are also embedded in other efforts, including retrofits and special projects. We are the spider in the web who helps manage on-time, in-scope security project execution while also ensuring projects comply with client expectations and standards. What do you enjoy most or find especially interesting about your current project/role? What’s not to like about supporting a globally relevant, Fortune 10 client?! The scope and scale of the work are awe-inspiring, the problem set is professionally challenging, and best of all, doing it with a team of stakeholders and vendors that are best in class at what they do. I’d like to think the work we are doing is important and meaningful in enabling the future of AI and future tech advancements, and we get to do it in a great environment with great people who help hold us accountable for excellence. How do you maintain a healthy work-life balance in your role? I’m new enough in the role that I’m still working towards work-life balance at the moment. If I look back on past experiences, I’ve found the most success with triaging priorities between what must happen now that only I can do, identifying where I can deputize others to help to carry the water, and also remembering that not everything can/needs to be accomplished right now. Also important to me is protecting time for both family and personal activities, like exercise. I find that I’m a lot more at ease working outside of core work hours as long as I’ve also engaged in core family activities and got my workout in. Tell us about something interesting you've learned recently. I recently read that scientists estimate there are significantly more trees on Earth than stars in the sky. Apparently, calculations are for over 3 trillion trees on Earth, compared to roughly “only” 300 billion stars in our galaxy. Besides struggling to comprehend any of these numbers, I am fascinated with the idea that there could be 10x as many trees on Earth as there are stars in the sky! If you could suggest a book for the entire team to read, what would it be and why? I think specifically for this audience, I’d suggest “Extreme Ownership” by Jocko Willink and Leif Babin. While the book is set against the backdrop of US Navy SEAL team operations, the core message that an effective leader leans into the problem and “owns everything” is very relevant to the multi-disciplinary client/vendor team environments we work in. It is too easy to blame missing a project milestone or deliverable on another dependency that didn’t meet its deadline. The book emphasizes that the best leaders don’t just take responsibility for their tasks or projects; they take an interest in and an ownership stake in everything that impacts their environment and their ability to succeed in the overall mission. I’d argue that the willingness to think outside your scope at core dependencies, and to anticipate and solve potential problems before they have an impact, brings tremendous value to our work and gets us invited back to the table as the problem solvers we want to be seen as. What's a piece of obsolete technology you still have a soft spot for? Not sure if this counts, but in a world where I walk into most meetings with 2 laptops and a smartphone, I still default to handwriting notes and tracking deliverables in my notebook. Additionally, I’m guilty of having multiple sticky notes on my laptop, helping me keep tabs on various action items or “great ideas” to follow up on at any given time. What's one thing people don't know about you that they would be surprised to discover? I have a great interest in wilderness adventure, including extended backpack treks, motorcycle road trips, and overlanding expeditions. As examples, I’ve traveled the AlCan highway and backcountry roads from Seattle to Alaska and the Arctic Ocean twice over the past several years. The first time was a solo motorcycle adventure from Seattle to Seward, AK. The second time was an overland expedition with my son from Seattle to Tuktoyaktuk, Northwest Territories, where we drove as far as we could in North America and dipped our toes in the Arctic Ocean. This was a 5000-mile road trip, over half of which was over dirt roads. What are you passionate about or enjoy outside of work? I am an active member of the King County Sheriff’s Search and Rescue Association, a 100% volunteer organization dedicated to locating and assisting individuals who are lost, injured, or in distress in wilderness, urban, and disaster environments. I participate in both the 4x4 unit and the Regional Specialty Vehicle Unit (RSVU), which includes ATV and SxS use in missions. It's my outlet to give back to the community while also getting me outdoors in the PNW with a fantastic group of dedicated, like-minded individuals.

Software development isn’t just evolving — the entire way organizations build solutions is being rewritten in real time. A year ago, “AI in development” meant faster autocomplete. Today, business managers can turn an idea into a working prototype before lunch, providing a clear blueprint for engineering to then fold into the final production code. For leaders, the shift isn’t about code. It’s about capability, speed, and who gets to build. Understanding this new landscape is now a strategic advantage. The Three Modes of AI-Assisted Development Vibe coding: software development by intuition and natural language. Describe what you want, the AI writes the code, and iterate by feel. Pro code: professional engineers using AI as a force multiplier inside coding software: completion, review, test generation, refactoring. Agentic engineering: AI doesn’t just suggest, it acts. Agents read the repo, plan changes, run tests, and open pull requests; humans manage and review. Why It Matters Beyond the Engineering Org This isn’t just an IT story, and the most underrated impact isn’t on engineers at all. It’s on everyone next to engineering. Take the Product Manager role. The PM job used to be write a spec, debate it, hand it to engineering, wait. The new PM job looks more like prompt an AI agent, get a working prototype in an hour, put it in front of a customer, refine, and then loop in engineering for the production build. The PM is no longer writing requirements; they’re orchestrating AI agents and validating with real artifacts. The implications ripple outward: The build/buy/wait calculus has changed. Custom internal tools that used to take a quarter and a six-figure budget can now ship in a week. That changes what’s worth building. Software fluency is becoming a core competency. Not “learn to code” but “learn to direct code.” The people who can clearly describe a problem and iterate with an AI will outpace those who can’t. Backlogs are getting unstuck. Every company has a list of “we should automate that someday.” Someday is now. The talent equation is shifting. Smaller teams are shipping more. Senior engineers are getting more leverage. PMs, analysts, designers, and ops folks are stepping into building roles that didn’t exist for them before. From “Wait” to “Create”: The New Workflow The traditional cycle — Idea → Plan → Design → Build → Test → Deploy is being replaced by something much tighter: Idea & Prompt. Brainstorm with the AI. Use it as a thinking partner, not just a builder. Vibe-Code a Prototype. Stand up a working version in hours using tools like Cursor, Replit, Google AI Studio, or Claude Code. Validate by Experience. Let stakeholders click through it rather than read about it. Refine & Deploy. Iterate with AI; harden the parts that need to live in production. The strategic shift is subtle but profound: alignment now happens around working artifacts, not documents. A clickable prototype kills more bad ideas and proves more good ones than any 12-page requirement document ever did. The Tooling Landscape A non-exhaustive snapshot of what’s worth knowing: GitHub Copilot — the default in coding app assistant for most professional developers. Strong at code completion, in-line chat, and increasingly at multi-file edits. Claude Code — Anthropic’s terminal-native agent that can read, edit, and execute across an entire codebase. Strong fit for agentic workflows and complex refactors. Cursor, Windsurf, Replit Agent — AI-native editors blurring the line between “vibe coding” and professional development. Google AI Studio, Gemini Code Assist, v0, Lovable, Bolt — fast prototyping environments aimed at non-engineers and PMs who want to skip the in-coding app entirely. Microsoft AI Studio / Azure AI Foundry — the enterprise platform for building, evaluating, and deploying custom AI agents and applications, with the governance and identity controls enterprise IT actually requires. The right answer is rarely one tool. It’s a stack, and it's changing every week. The New Skills That Actually Matter For everyone now in the building seat, not just engineers, a few capabilities are quickly becoming non-negotiable: Prompt craft. Precise, context-rich instruction is the new technical writing. Systems thinking. AI writes the code. Humans still need to understand data flow, system boundaries, and integration points; otherwise, you get fast spaghetti instead of slow spaghetti. Setting constraints, not just features. Telling the AI what not to do, what file structure to follow, and what architecture to honor matters as much as describing the feature itself. Knowing when not to use AI. Some problems still need human creativity, taste, or domain judgment. The most effective practitioners can tell the difference. The shift is bigger than faster coding. It’s a new operating model for how ideas become software — and who gets to participate. But opportunity is only half the story. The other half is the discipline required to build safely, securely, and sustainably in this new world. Part 2 of this series digs into the realities: where AI accelerates, where it breaks, and what leaders need to get right.

AI has reached an inflection point. The excitement hasn’t disappeared, but the novelty has. Leaders are no longer rewarded for experimenting; they’re expected to show outcomes. And as it shifts from “shiny new thing” to standard part of the workflow, we’re reminded of an age-old truth: technology alone won’t move your organization forward. What matters now is whether your AI investments are anchored to purpose, values, and the real work your teams are responsible for. That’s where change discipline becomes the differentiator. AI Is a Tool. Purpose Is the Point. Change principle: Investments must advance mission, values, and goals, or they will be rejected or ignored. AI has moved rapidly from shiny to standard, and that shift is healthy. Once the novelty fades, we can treat AI the way we treat every other transformative tool. Commercialized planes, electricity, and the internet changed what was possible, but none of them was a strategy in itself. The real question isn’t “Do we have AI?” It’s “What does this unlock for our mission, values, and goals?” Values Are Not a Poster. They Are a Design Requirement. Change principle: Change succeeds when it aligns with what the organization values and how the work must be done. This is where many efforts drift. Leaders approve tools, teams start experimenting, and the organization hopes value will appear. But innovation only sticks when it attaches to the real expectations of the work. If your team is creative, solutions must protect creative integrity while accelerating the process. If your team safeguards physical security at data centers, innovation must increase trust and visibility—not weaken them. If your team leads digital transformation, AI should enhance engagement, speed innovation, and limit disruption. Different missions require different boundaries, measures, and behaviors. AI must serve the work, not the other way around. Discipline Is the Differentiator When AI Is No Longer Shiny. Change principle: Change is the catalyst that turns capability into outcomes through clear decisions and consistent implementation. Most organizations can buy the tools. Far fewer can convert them into a reliable way of working. That conversion is change discipline. Change discipline looks like: Leaders making intent explicit Clear decisions about where work will change and where it will not Ethical boundaries that protect trust Reinforcement until new behaviors become normal Data and systems coherent enough to support the new ways of working Tools don’t create outcomes. Discipline does. What Leaders Must Make Explicit. Change principle: Clarity creates momentum by giving people permission to act inside defined guardrails. Start with three statements people can repeat: What investment is meant to unlock What values must it protect What “good” looks like in day‑to‑day work Then back those statements with visible decisions: Which workflows change first? Which roles get trained and reinforced? What measures prove progress against the mission? AI will keep improving. Your advantage won’t come from chasing the next model. It will come from disciplined change that consistently turns investment into outcomes that matter. To learn more about how to translate AI intent into new ways of working, contact RedCloud’s Business Transformation Services Practice team.

As a key member of our rapidly growing European team, Lovisa Nyman brings a rare blend of structure, curiosity, and global perspective to her role as Global PMO Lead for RedCloud’s Physical Security practice. Her work sits at the heart of the program’s operational rhythm—turning complex project data into clarity, building processes that actually work, and spotting opportunities for improvement before anyone else sees them. In this conversation, she shares what energizes her about the role, how she balances a truly global schedule, and the unexpected life experiences that shaped her approach to problem-solving. It’s a glimpse into the mindset of someone who quietly keeps an entire program running smoothly while never losing sight of what matters most outside of work. Describe your role and what you do in a nutshell. My work as a Global Project Management Office (PMO) Lead involves reporting on the projects our Physical Security TPMs are working on to ensure we capture all required data throughout the projects and at project close-out, as well as project forecasting for the leads and Technical Program Managers (TPMs) to plan workload. Process improvement is also a big part of the PMO's day-to-day work, ensuring we have clear processes to follow so projects run as smoothly as possible. Data and reports are being created and automated to ensure all data we need is easily accessible and up to date. What do you enjoy most or find especially interesting about your current role? The possibility of seeing a gap, a process not working, or getting a new idea of what can be improved, and being able to create what's needed to make an improvement. The flexibility of figuring out what’s needed after discussions with the team and the leads, and creating something that will support the whole team and program. How do you maintain a healthy work-life balance in your role? Being global makes the workdays look different day to day, depending on meetings and what is currently going on. Therefore, I usually work out during my lunch breaks to clear my head after a morning of working with Asia-Pacific (APAC) and Europe, the Middle East and Africa (EMEA), and get a refresh and some energy for later meetings when North America/South America (NASA) wakes up. What's one thing people don't know about you that they would be surprised to discover? When I studied, I moved to Mexico for one semester to study and learn Spanish. Being from Sweden, this is something that often surprises people. I left my then-boyfriend, now husband, at home for half a year and moved to a country where I did not know the language. It taught me that you can always figure things out, despite how challenging they are. What are you passionate about or enjoy outside of work? I’ve always liked being active and working out to get energy. Lately, as I build a family, it’s also about spending quality time with my husband and daughter and experiencing things through her eyes.

As global data center expansion accelerates, the stakes for physical security have never been higher. Hyperscalers are delivering facilities across multiple regions simultaneously, often with mixed delivery models—owned, leased, and colocated environments operating in parallel. That complexity introduces real risk: inconsistent standards, uneven installation quality, and gaps between design intent and what’s actually delivered on the ground. At RedCloud, we approach this challenge with a simple principle: no single control should determine the success or failure of a security program. Instead, we structure physical security delivery around a layered defense model—one that validates coverage holistically, from early design through operational readiness. Below is the framework our teams use to ensure every facility is protected with rigor, consistency, and resilience. 1. Site & Boundary Controls Every secure environment begins with the land it sits on. Site selection, boundary definition, and environmental constraints shape the entire security strategy. By evaluating these factors early, RedCloud ensures that physical security is built on a strong foundation—not retrofitted as an afterthought. 2. Perimeter Protection The perimeter is the first line of defense. Fencing, barriers, gates, vehicle controls, and intrusion detection systems work together to deter and delay unauthorized access. Our teams validate that these controls are installed correctly, integrated properly, and aligned with global standards. 3. Access Control Systems People and vehicles move through facilities constantly. Badging, biometrics, and controlled entry points ensure that only authorized individuals can enter sensitive areas. RedCloud’s delivery oversight ensures these systems are configured, tested, and documented with precision. 4. Surveillance & Detection Visibility is non‑negotiable. Cameras, monitoring systems, and detection technologies provide real‑time awareness across critical zones. We ensure that surveillance coverage is complete, functional, and integrated with broader security operations. 5. Building & Interior Zoning Not all spaces are created equal. Interior zoning separates public, semi‑secure, and highly secure areas, reducing risk and improving incident response. RedCloud validates that zoning aligns with design intent and that transitions between zones are properly controlled. 6. Critical Area Protection Data halls, cages, and control rooms require the highest level of protection. These areas house the infrastructure that keeps global platforms running. Our teams ensure that every critical zone meets stringent security requirements and passes readiness checks before go‑live. 7. Operational Readiness & Response Security doesn’t end at installation. Procedures, escalation paths, and integration with operations teams ensure that controls work in practice—not just on paper. RedCloud’s delivery model includes readiness validation, scenario testing, and cross‑team alignment to ensure long‑term resilience. A Holistic Approach to Security Delivery Physical security is only as strong as its weakest link. By applying a layered defense model, RedCloud ensures that every control—technical, procedural, and operational—works together to protect the world’s most critical infrastructure. From design reviews to vendor coordination to on‑site validation, our teams bring clarity, consistency, and rigor to every stage of delivery. The result: secure, scalable, and operationally ready facilities that meet the demands of a rapidly expanding global footprint.

AI capabilities are advancing faster than most organizations can absorb, but the real bottleneck isn’t the technology. It’s the absence of clear leadership direction. Teams are being handed powerful tools without a shared understanding of how decisions, priorities, or workflows are expected to change. As a result, value stalls in the middle of the organization—not because people resist the tools, but because they don’t know what “good” looks like. When leaders don’t define intent, AI defaults to an efficiency story. That framing may feel pragmatic at the executive level, but it often comes across as a risk to employees. Without a connection to growth, innovation, reskilling, or mission, the language of efficiency creates fear rather than momentum. And when that fear goes unaddressed, teams shift into a cautious mode while the tools continue to advance. Where AI Value Breaks Most organizations aren’t failing at AI because the technology is weak. The tools are ready. What’s missing is clarity on how work is expected to change—and how quickly. Turning on Copilot or Gemini is not the same as defining new ways of working. Without direction, teams stay in experimentation mode: testing prompts, sharing tips, and layering new tools onto old habits. Adoption looks slow, but the real issue is that the work being done adds little value because intent was never defined. Efficiency framing creates a second barrier. When AI is positioned primarily as a cost play, the conversation narrows. Teams shift from exploring what’s possible to protecting what exists. Instead of experimenting, they hesitate, wait for clearer signals, and limit their use of the tools. Adoption may look slow, but the real issue is that the narrative pushed people toward caution rather than opportunity. A Practical Starting Point: Signal to Insight One of AI’s most powerful capabilities is collapsing the time between signal and insight. People can orient to problems faster, explore options more quickly, and surface patterns that once took weeks to uncover. This makes signal-to-insight a practical starting point for AI enablement before redesigning workflows or operating models. As organizations accelerate, a second challenge emerges: the velocity gap. High performers adopt AI quickly and take on more because they can. What doesn’t scale is cognitive and relational capacity. People begin operating faster than they can think, align, or make sense. This gap creates real risk to culture, accountability, and sustained performance. What Leaders Must Make Explicit AI value is ultimately human-driven. Technology doesn’t replace judgment; it depends on it. Context, learning, reinforcement, and shared understanding are what make capability usable. The real lever is scale. High performers already show what “good” looks like; the opportunity is making those behaviors standard across the organization. When AI fluency becomes widespread, value compounds quickly. Direction is a leadership responsibility. Leaders can manage risk and unlock value when they are explicit about where AI is expected to change work and where it is not. That clarity reduces confusion and gives teams permission to move. Transformation partners help translate intent into new ways of working without requiring perfect answers upfront. Progress doesn’t come from a flawless plan. It comes from leaders willing to acknowledge uncertainty, ask for help, and engage their directors in honest conversations. By identifying where the velocity gap is emerging and deliberately shaping new ways of working, organizations can turn recent AI investments from latent capability into real, measurable value. To learn more about how to translate AI intent into new ways of working, contact RedCloud’s Business Transformation Services Practice team.

Rafik Pathan is one of the driving forces behind physical security design across EMEA, ensuring some of the world’s most advanced data centres are built to an uncompromising global standard. As a Physical Security Design TPM, he bridges global strategy and regional engineering, guiding complex projects from concept to construction with precision and a calm, authoritative approach. Outside of work, he’s a lifelong learner, a lover of retro tech, and a devoted Manchester United fan who still makes time for family, fitness, and the occasional nostalgic Minidisc moment. Read on to learn more about one of our key team members on our rapidly expanding European team.  Describe your role and what you do in a nutshell. I’m a Physical Security Design TPM supporting data centre rollout across EMEA. I provide technical oversight of electronic security designs, making sure global standards are correctly implemented by regional AE firms while meeting local regulations. I’m the link between the client’s global security team and regional engineers, resolving design issues and ensuring local adaptations never weaken the global security framework. I guide projects through to IFC, ensuring drawings and specifications are accurate, build‑ready, and consistent across the EMEA portfolio. What do you enjoy most or find especially interesting about your current project? I enjoy the challenge of maintaining one gold‑standard security framework across such a diverse region. Every project requires balancing global specifications with local codes and site conditions—without ever lowering the security bar. How do you maintain a healthy work-life balance in your role? I’m a big believer in staying active to keep a clear head. I enjoy walking and spending time in the gym—whether running or doing yoga—as it’s the perfect way to reset after a busy day. Above all, I value spending quality time with my family. They keep me grounded and provide the greatest rewards outside of my professional life. Tell us about something interesting you've learned recently. One of the most interesting developments I’ve experienced recently is the shift toward fully remote design governance for physical security across data centres in the EMEA region. Managing this remotely has fundamentally changed how we collaborate with engineering teams. We’re now using far more sophisticated digital capture and visualisation technologies, and it’s fascinating to virtually walk through a facility in Spain or Finland to verify design details without being on site. This approach has made design reviews faster and more precise, allowing me to provide the client with near real-time technical oversight across multiple projects and countries while maintaining the same high standards. If you could suggest a book for the entire team to read, what would it be and why? 1984 by George Orwell. We essentially build high‑security vaults for the world’s collective memory. If Orwell had imagined Big Brother obsessing over ANSI/ISO/EN standards, redundancy, and making sure no one trips over a power cable, that would be my day job. I keep the “Fort Knox of Fiber‑Optics” secure—less thoughtcrime, more biometric integrity and anti‑tailgating. Very “Ministry of Truth,” but with better health and safety. What's a piece of obsolete technology you still have a soft spot for? The Minidisc. It is the quintessential digital heirloom, seamlessly marrying the satisfyingly mechanical "clack" of a high-spec cartridge with a retro‑futuristic aesthetic that transforms music from a fleeting, disposable stream into a deliberate and physical treasure. In an era of invisible algorithms, the Minidisc stands as a defiant nod to British "shed‑hobbyist" culture, offering a tactile, hands‑on experience where one actually owns the media rather than merely licensing it, all wrapped in a robust, cyberpunk‑inspired shell that still feels like a prop from a high‑budget sci‑fi film. Mix tapes for the ages. What's one thing people don't know about you that they would be surprised to discover? When I was younger, my uncle was an up-and-coming actor appearing in some very well-known British TV shows, and he introduced me to the world of film. Through him, I was lucky enough to spend time on a few major movie sets as an extra. It felt pretty magical at the time, and it also meant I had the chance to meet a few of my heroes along the way. Looking back now, it’s an incredible experience to have had a glimpse behind the scenes of such big productions at such a young age. What are you passionate about or enjoy outside of work? Manchester United. Whenever I can, I’ll make the drive up to the Theatre of Dreams. There’s nothing quite like being there in person when the atmosphere is electric. Manchester United's identity is built on a legacy of youth and resilience, from the tragic Munich air disaster that claimed eight Busby Babes in 1958 to the rise of the "Holy Trinity"—Sir Bobby Charlton, Denis Law, and George Best—who led the club to its first European Cup in 1968. This tradition was revitalised under Sir Alex Ferguson, whose 26-year tenure yielded 38 trophies and was anchored by the homegrown Class of '92 (Ryan Giggs, Paul Scholes, and David Beckham). Key transformative figures like Roy Keane and Eric Cantona drove the 1990s dominance, while the explosive partnership of Wayne Rooney, the club's all-time top scorer, and Cristiano Ronaldo, who won his first Ballon d'Or at the club, defined a second golden era of Premier League and Champions League success.