It’s Possible. It’s Okta.

Read the campaign story

It’s Possible. It’s Okta. is documented as a 2024 campaign in creator Jenn Schmukler’s portfolio. The platform presented identity technology as a way to enable work rather than only a defensive obstacle. Brandon De Jong describes creative direction and a modular system for international use. The MX Group’s retrospective also documents its role in the broader campaign and media programme.

Scholar’s production account describes films built around Jenny, an approachable advocate who exchanges humorous remarks with a voiceover. Scholar says it developed, wrote and directed this work with Okta. These films and later Jenny extensions belong to the same platform. The old brand-blog URLs now redirect to category pages, so the case relies on readable creator and agency records rather than treating missing articles as verified evidence.

Editorial interpretation: a security brand can explain what becomes possible without denying that risks exist. This changes the conversation from an abstract threat to a practical decision about how people access tools. Humour may help audiences stay with the explanation, particularly when the subject normally arrives as jargon. The important test is whether people understand the mechanism after the joke, not simply whether they remember the character.

Editorial interpretation: the phrase needs careful boundaries. Faster access and stronger controls can coexist in a well-designed system, but every organisation still has configuration, implementation and governance requirements. Advertising should not imply that secure identity eliminates all friction or prevents every incident. A credible campaign can make the business value accessible while offering a clear route to technical evaluation for the people responsible for deployment. Any sales enablement version should retain those limitations rather than strip them away to make a shorter pitch. The audience’s confidence should come from understanding, not from missing qualifications.

Explain a real trade-off without pretending it disappears

Identify one situation in which users experience security as an obstacle, then show how a specific design changes that experience. Include the conditions under which the benefit holds. Avoid replacing fear-based exaggeration with optimism-based exaggeration. A well-scoped example can persuade both business and technical audiences because it gives each a concrete claim to inspect rather than an undefined promise to trust.

Give the character an explanatory responsibility

A recurring spokesperson should help viewers follow a decision or understand a term. Write the technical explanation first, then use humour to make its sequence easier to watch. Test comprehension with non-specialists and review accuracy with practitioners. If removing the jokes reveals no meaningful explanation, the character is functioning as decoration rather than making a complicated service more understandable.

Make campaign systems usable by local teams

A modular platform needs more than a logo file and an approved headline. Provide examples of permitted claims, technical caveats, audience-specific explanations and ways to adapt the format without changing the promise. Regional teams should know what requires expert review. This protects consistency while allowing local relevance, and reduces the chance that a concise central idea becomes an unsupported claim in a sales presentation.

A small test for another brief

Proposed adaptation: produce a short, fictional access-management scenario comparing a jargon-heavy explanation with a plain-language character-led version of the same approved capability.

Measure correct explanation of the capability, recognition of implementation requirements and interest in a technical evaluation. Track misunderstandings as seriously as positive reactions.

Stop if viewers infer guaranteed protection, no implementation effort or permission to bypass security controls. Do not trade technical accuracy for a more entertaining edit.

• Use a mock interface and synthetic identities; never demonstrate on live customer systems.
• Have security and product specialists approve the precise capability and limitations.
• Test with both business stakeholders and technical evaluators before publishing more broadly.