Update index.html

ronnie-bailey · web-flow · commit 0cc9184be5db · 2026-04-30T19:20:17.000-04:00
diff --git a/index.html b/index.html
@@ -3,7 +3,7 @@
 <head>
     <meta charset="utf-8"/>
     <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
-    <title>Ronnie Bailey: Lead Identity Security Architect</title>
+    <title>Ronnie Bailey | Identity Security Director</title>
     <link href="https://fonts.googleapis.com" rel="preconnect"/>
     <link crossorigin="" href="https://fonts.gstatic.com" rel="preconnect"/>
     <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=Courier+Prime:wght@400;700&display=swap" rel="stylesheet"/>
@@ -722,9 +722,6 @@
                     <span class="availability-text">Actively Seeking</span>
                 </div>
                 <div class="contact-icons">
-                    <a href="tel:+18046109719" title="Call me">
-                        <i class="fas fa-phone"></i>
-                    </a>
                     <a href="mailto:opportunities@ronniebailey.cloud" title="Email me">
                         <i class="fas fa-envelope"></i>
                     </a>
@@ -756,41 +753,33 @@
         <section class="hero">
             <h1>Ronnie Bailey</h1>
             <div class="hero-subtitle">
-                Lead Identity Security Architect
+                Identity Security Director
             </div>
             <p>
                 15 years shaping how enterprise organizations secure, govern, and scale identity. Across Fortune 500 firms, federal agencies, and critical infrastructure, the work has always been the same at its core: make identity the thing that holds when everything else is under pressure.
             </p>
 
             <div class="hero-links">
-                <a href="contact.html" target="_blank" class="hero-link" title="Get in touch">
-                    <i class="fab fa-github hero-link-icon"></i>
-                    <span>Contact</span>
-                </a>
-                <a href="soon.html" target="_blank" class="hero-link" title="Read my IAM insights blog">
-                    <i class="fas fa-pen-nib hero-link-icon"></i>
-                    <span>IAM Insights Blog</span>
-                </a>
-                <a href="https://cloudcentria.com/work.html" class="hero-link" title="View detailed case studies">
-                    <i class="fas fa-chart-line hero-link-icon"></i>
-                    <span>Case Studies</span>
+                <a href="contact.html" class="hero-link" title="Get in touch">
+                    <i class="fas fa-envelope hero-link-icon"></i>
+                    <span>Let's Connect</span>
                 </a>
             </div>
         </section>
 
         <section id="perspective" class="perspective-section">
             <h2 class="section-title">Perspective</h2>
             <p>
-                To me, identity should not just be considered a product you deploy. I have come to learn that identity is a decision framework that runs underneath everything your organization does — who gets in, what they can touch, when that access ends, and what happens when something breaks. In my experience most organizations treat it as infrastructure, however the ones that get it right understand and treat it as policy. To me it is an important distinction and more of a necessity than any tool in the stack.
+                The hardest problems in identity are rarely technical. The technical problems have answers. The hard problems are organizational: nobody owns the policy, the accountability structure was never defined, the exception became the rule, and by the time someone notices the debt is structural.
             </p>
             <p>
-                What I have learned across 15 years of this work is that the hardest problems in identity are rarely technical. The technical problems have answers. The hard problems are organizational: nobody owns the policy, the accountability structure was never defined, the exception became the rule, and by the time someone notices the debt is structural. My value is in knowing how to walk into an environment where identity was built by ten different people over ten years and make it coherent, defensible, and owned.
+                My value is in knowing how to walk into an environment where identity was built by ten different people over ten years and make it coherent, defensible, and owned.
             </p>
             <p>
-                I think about identity security the way a good architect thinks about a building. The foundation has to be sound before you add floors. Zero Trust is often used as a buzzword but in my experience it is a posture you earn incrementally by making every access decision explicit and every privilege temporary. That work is unglamorous and it is constant however it is the difference between an organization that knows its exposure and one that finds out during an incident.
+                Zero Trust is often used as a buzzword. In practice it is a posture you earn incrementally by making every access decision explicit and every privilege temporary. That is the difference between an organization that knows its exposure and one that finds out during an incident.
             </p>
             <p>
-                The most important work I do now is translate. Technology decisions that are not understood by the people who fund them get defunded when priorities shift. Risk that is not legible to a CISO or a board does not get mitigated but usually ends up inherited by the next team. My role is to ensure that doesn't happen by bridging the gap between technical realities and business decisions so they stay aligned.
+                The most important work I do is translate. Technology decisions that are not understood by the people who fund them get defunded when priorities shift. Risk that is not legible to a CISO or a board does not get mitigated and usually ends up inherited by the next team. I own these programs end to end: governance, Zero Trust architecture, privileged access, federation, lifecycle management, and the CISO conversation that ties it all together. I can design the framework and I can also open a sign-in log and find what is breaking before it becomes an incident.
             </p>
         </section>
 
@@ -836,7 +825,7 @@ <h2 class="section-title">Professional Experience</h2>
             </div>
 
             <div class="experience-item">
-                <div class="job-title">Lead Identity Security Architect</div>
+                <div class="job-title">Identity Security Director</div>
                 <div class="company-name">
                     LexisNexis / United States Patent and Trademark Office
                 </div>
@@ -1188,7 +1177,7 @@ <h2 class="section-title">Cybersecurity News & Insights</h2>
     </div>
 
     <footer>
-        <p>&copy; 2025 Ronnie Bailey | Lead Identity Security Architect</p>
+        <p>&copy; 2025 Ronnie Bailey | Identity Security Director</p>
     </footer>
 
     <script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script><script>
