organizational-transformation
Help users transform organizations toward modern product practices. Use when someone is trying to shift from feature teams to product teams, introduce empowered teams, modernize legacy processes, or drive cultural change in how product is built.
What this skill does
# Organizational Transformation Help the user transform their organization toward modern product practices using insights from 2 product leaders. ## How to Help When the user asks for help with organizational transformation: 1. **Understand their starting point** - Ask what their current model looks like (feature teams, output focus, waterfall) and what's driving the need for change 2. **Diagnose readiness** - Determine who has the authority and will to drive change, and what resistance they should expect 3. **Design the approach** - Help them decide between pilot teams, gradual nudges, or broader transformation initiatives 4. **Manage the change** - Guide them on communicating, measuring progress, and handling resistance ## Core Principles ### Frameworks are means, not ends John Cutler: "Most companies see adopting frameworks as the end goal." The goal is better outcomes, not implementing Scrum or SAFe or any specific methodology. Evaluate frameworks by whether they help your specific organization solve its specific problems. ### Transform through pilots, then spread Marty Cagan: "The goal of TRANSFORMED was to share how to actually change - transformation techniques." Start with a small number of empowered product teams that can demonstrate the model works. Use their success to build credibility for broader change. ### Nudge legacy companies carefully John Cutler emphasizes "nudging" non-Silicon Valley companies toward modern practices without causing systemic rejection. Radical change proposals often get rejected. Find ways to introduce new practices that don't threaten existing power structures. ### It's structural, cultural, AND process change Marty Cagan describes moving from "feature teams" to a "product operating model" - this requires changing structures (how teams are organized), culture (how people think about their work), and processes (how decisions get made). Changing only one dimension won't work. ## Questions to Help Users - "What's driving the need for transformation? What's broken today?" - "Who has the authority and will to sponsor this change?" - "What's your current model - feature teams, waterfall, something else?" - "Where would you start? Is there a team or area that could pilot the new approach?" - "What resistance should you expect, and from whom?" - "How will you know if the transformation is working?" ## Common Mistakes to Flag - **Treating framework adoption as the goal** - Implementing Scrum doesn't mean you've transformed. Focus on outcomes, not ceremonies - **Big-bang transformation** - Trying to change everything at once usually fails. Start with pilots - **Ignoring culture** - Process changes without cultural change get worked around. Address beliefs, not just behaviors - **No executive sponsorship** - Transformation without senior support gets crushed by organizational antibodies - **Copying Silicon Valley blindly** - What works at Google may not work at a 50-year-old enterprise. Adapt, don't copy ## Deep Dive For all 2 insights from 2 guests, see `references/guest-insights.md` ## Related Skills - Organizational Design - Building Team Culture - Managing Up - Having Difficult Conversations
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.