Interview with Jordan Lee, Head of Creative Strategy at FortiSecure

Q: Jordan, many teams assume cross-functional workflow design is just a matter of assembling diverse talent and setting up meetings. What do senior creative directors in cybersecurity often get wrong about this?

Jordan Lee: The biggest misconception is treating cross-functional workflows like a one-off project or a simple handoff mechanism. Too often, teams see it as “get engineering, product, and design together, then let them figure it out.” This usually breeds friction, duplicated effort, or scope creep.

Cross-functional workflow design is a multi-year commitment. It’s about aligning evolving goals, adapting to shifting threat landscapes, and maintaining a shared language across disciplines. For example, a 2023 Gartner study found that 62% of cybersecurity product teams failed to meet their roadmap milestones because cross-team dependencies weren’t continuously managed.

This isn’t just process hygiene; it’s about sustainable growth. If you build workflows that only solve immediate friction points, you create brittle systems that collapse under scale or new initiatives.

Q: What are the foundational steps creative leads should prioritize for a long-term, cross-functional workflow in security software?

Jordan Lee: You have to start with vision alignment at the leadership level. That means everyone from CISO to the lead UX designer understands the multi-year mission. In cybersecurity, this mission could involve developing adaptive threat models or evolving zero-trust architectures—both require continuous iteration and integration.

Secondly, define clear shared metrics that aren’t siloed. For example, instead of just product delivery timelines, track post-release detection accuracy improvements or reductions in false positive rates, which require collaboration between data scientists, engineers, and marketing.

Third, establish a tiered feedback framework. Quarterly reviews with qualitative inputs, supported by continuous pulse checks through tools like Zigpoll or Culture Amp, help catch misalignments early. One team at CyberGuard Analytics improved cross-team satisfaction from 52% to 78% within 18 months by instituting such mechanisms.

Q: How do you maintain flexibility in workflows without sacrificing clarity or accountability?

Jordan Lee: Flexibility is often misunderstood as “loosening deadlines” or “no defined roles.” That’s a recipe for chaos in security software, where compliance and risk management demand rigor.

Instead, design modular workflows. Think of them like microservices in software: each function owns discrete responsibilities, documented in playbooks but adaptable within guardrails. For example, engineering owns code hardening, but design manages user experience for security alerts. Each can evolve their processes independently yet align on integration points.

Regular cadence meetings—weekly syncs, monthly retrospectives—must be balanced so they don’t become overhead. One cybersecurity client reduced cross-functional meeting time by 23% by introducing rolling agendas focused on blocking issues only, boosting throughput.

Q: Cross-functional work often surfaces conflicting priorities. What techniques can creative directors use to resolve these tensions productively?

Jordan Lee: I recommend embracing the tension instead of trying to eliminate it. In cybersecurity, the trade-off between usability and security is perennial. Instead of aiming for perfect consensus, create an escalation path for “tension points” with transparent criteria.

Use scenario-based workshops where teams simulate attack or failure modes to highlight risks and user pain points simultaneously. This grounds debates in data and shared goals instead of opinion.

Furthermore, quantifying impact helps. For instance, if marketing wants faster feature launches but engineering signals a vulnerability risk, run a quick risk-reward analysis using threat modeling data. It’s not about one side winning but collaboratively balancing constraints.

Q: Could you elaborate on how to leverage data for cross-functional workflow optimization over multiple years?

Jordan Lee: Absolutely. Data is underutilized when it’s only reactive, like postmortems or customer complaints. Proactive metrics—such as Mean Time to Detect (MTTD) and Mean Time to Respond (MTTR) within development cycles—should feed back into workflows constantly.

One example: a security platform improved its MTTD by 30% over two years by integrating telemetry from SOC (Security Operations Center) analysts directly into product development sprints. This required setting up cross-team dashboards updated weekly and making response times a shared goal.

However, the downside is data overload. Many teams drown in dashboards that don’t drive decisions. Prioritize a few leading indicators that directly affect your long-term roadmap and reinforce those in team rituals.

Q: How do you see tooling evolving to support these workflows, and when should creative directors push for new solutions?

Jordan Lee: Tool proliferation is a serious risk. In cybersecurity, teams juggle SIEMs, vulnerability scanners, ticketing systems, and collaboration platforms. Adding more tools often creates friction rather than solves it.

Creative directors should focus on interoperability and integration over new standalone tools. For example, embedding automated data flows between Jira, Slack, and vulnerability management platforms prevents silos and context loss.

Push for new tooling only when the existing stack creates bottlenecks that impede roadmap milestones or causes repeated human error. For instance, introducing a unified feedback platform like Zigpoll can dovetail into sprint retrospectives, improving cross-team sentiment analysis without adding extra layers.

Q: What common pitfalls should senior creative directors avoid when designing cross-functional workflows for long-term growth?

Jordan Lee: Over-engineering workflows is one. Creating overly complex RACI matrices or rigid approval gates can stifle innovation and slow responses to cyber threats that evolve rapidly.

Another is ignoring cultural differences across functions. Security researchers, product managers, and marketing teams speak different “languages.” Don’t expect alignment by decree—invest in shared glossaries, joint onboarding sessions, and ongoing culture calibration.

Finally, beware of treating workflow design as a quarterly task. It requires continuous iteration informed by data, emerging tech, and shifting threat vectors. Neglect this and the workflow becomes outdated as your product and ecosystem mature.

Q: Can you share some actionable advice or first steps for creative directors ready to tackle this challenge?

Jordan Lee: Start with mapping the current state. Conduct stakeholder interviews and document pain points, bottlenecks, and dependencies. Use tools like Zigpoll to gather anonymous feedback on collaboration effectiveness.

Next, align leadership on a 3-5 year vision that connects product innovation with compliance and customer trust goals.

Pilot modular workflows within a single product vertical or team, then measure the impact on cross-team KPIs such as defect leakage rates or feature adoption speed.

Finally, build in regular retrospectives focused solely on workflow health, not just product delivery. This keeps your long-term strategy adaptable as cybersecurity landscapes shift.

Comparison Table: Workflow Design Approaches for Long-Term Cybersecurity Growth

Jordan Lee’s insights push us to rethink cross-functional workflows not as a checklist but a living, evolving system crucial to meeting the demands of cybersecurity’s dynamic threat environment. Senior creative directors who anchor their strategy in long-term vision, clear shared goals, and adaptive feedback are best positioned to sustain growth and innovation.