Executive Summary
This discussion centered around aligning the Gobo platform's development roadmap with recent organizational changes and executive priorities. With the recent infrastructure reorg dividing responsibilities between Solutions Design (Daniel's group) and Security Network Operations (David's group), Gobo needs to prove its value by shifting away from redundant basic monitoring and focusing on actionable intelligence through cross-platform data aggregation.
The Gobo Strategy
Core Philosophy: Don't recreate the wheel. Gobo must be the "Easy Button" that aggregates data from siloed tools to provide insights that no single tool can offer alone.
Initiative 1: The Universal IP Context Search
The Problem: Current IPAM has fundamentally failed. When security/SOC flags an IP address, nobody knows what site it belongs to, what hardware it runs on, or who the point of contact is.
The Solution: Build a simple, Google-like search bar in Gobo. Enter an IP, and Gobo aggregates data across systems to instantly output: Physical Location, Hardware Type (FortiGate/Cisco), Running Services, and Bureau/Local Point of Contact. This directly appeals to executive desires for network visibility.
Initiative 2: Unified Helpdesk Troubleshooting Dashboard
The Problem: Rolling out new 802.1x network access control (NAC) and Wi-Fi creates complex troubleshooting for the Helpdesk, involving multiple siloed platforms.
The Solution: Integrate APIs from the "Trifecta": Meraki (Wi-Fi) + Cisco ISE (Auth) + MS Intune (Endpoint). Give Customer Support a single dashboard to see exactly why a user's connection is failing. Getting helpdesk staff reliant on Gobo guarantees its long-term survival.
Key Takeaways
-
Avoid Basic Site Monitoring
Building a basic "up/down" site monitor in Gobo is a waste of cycles. Tools like Acunetix already exist for this. Gobo must focus on higher-level correlation.
-
Lumen is on the Outskirts
The vendor Lumen has denied API access to their web help desk, likely out of self-preservation. Leadership intends to part ways with Lumen "with prejudice," meaning Gobo shouldn't prioritize building dependencies around their tools.
-
New Reorg Dynamics
The team is settling into a new structure. Daniel's team handles architecture/solutions design, while David's team handles operational security (e.g., ZTNA operations). There is some friction with legacy "old school" engineers resisting new architectures.
-
API Integration Focus
Immediate next steps for the Gobo dev team involve securing API access and keys for MS Intune (via Troy Cobb), Cisco ISE (via Harrington's crew), and utilizing the newly acquired Meraki API keys.
Executive Profile
Subject: RICK
Role & Influence
Senior executive, boss of Jen. Wields immense authority over technological direction and vendor relations.
Persona & Style
Described as highly unpredictable ("wild," "loose cannon"). He is heavily involved, desires to be hands-on, and views himself as a technologist. He expects real-time visual proof of work.
Known Preferences
- Likes to log into platforms directly (requested direct access to SolarWinds, Meraki, and Cisco ISE portals).
- Values high-level statistics, dashboard numbers, and logical visual organization.
- Adamantly anti-Lumen; wants the vendor fired "with prejudice."
Management Strategy: "The Pivot"
Rick frequently issues technically unsound or massive directives (e.g., "re-address the entire IPv4 network so IPs logically correspond to locations"). The team's strategy is to pivot these directives into best-practice engineering (e.g., implementing IPv6 Greenfield translation for logical segmentation) to satisfy his intent while deploying actual, beneficial architecture.