Elizabeth Carpenter

SELF-DIRECTED CONCEPT / CYBERSECURITY COMMUNICATIONS / SEPTEMBER 2026

FIRST HOUR.
Start the conversation
before the incident.

A campaign concept inviting small nonprofit teams to practice the communication decisions that follow a suspected cyber incident.

Fictional brief and original portfolio creative. This is an independent exercise, not an employer project, a product demonstration, or a record of a live campaign. The workshop and all numerical targets below are proposed.

Creative remit
Audience framing, positioning, copy, visual direction, campaign sequencing, and measurement design.
Fictional audience
Nonprofit operations and IT managers working with small teams and limited time.
Assignment
Design a four-week invitation campaign for a proposed 30-minute discussion exercise.

FIRST HOUR / A READINESS CONVERSATION

Who gets the
first call?

A short exercise. A clearer contact plan.
Bring your IT and operations leads to the same conversation.

CAMPAIGN KEY VISUAL / ORIGINAL CONCEPT

01 / THE BRIEF

Make preparation feel manageable.

The fictional sponsor is a small cybersecurity training provider introducing a facilitated discussion for nonprofit teams. The business objective is to earn relevant workshop registrations and identify organizations that want a follow-up conversation.

My audience hypothesis: an operations manager is more likely to consider a specific, time-bounded activity than a broad invitation to “transform cybersecurity.” That hypothesis would need validation with prospective participants.

02 / STRATEGY

One practical question opens the door.

TIME

Can this fit into our week?

State the proposed 30-minute format in the invitation and make preparation expectations explicit.

RELEVANCE

Is this for a team like ours?

Address operations and IT together. Keep the scenario focused on responsibilities and communication.

CONFIDENCE

Will this turn into a sales pitch?

Explain the agenda and the take-away before asking for a registration. Offer follow-up only by request.

VALUE

What will we leave with?

Offer a draft contact map and a list of unanswered questions to take back to the organization.

03 / ORIGINAL EXECUTION

One invitation, adapted to the moment.

Live text and restrained typography keep the samples readable. These are original creative examples for the fictional brief.

SOCIAL POST / SAMPLE COPY

Who gets the first call?

A suspicious message lands. A colleague asks what to do. Does everyone know who should hear about it first?

FIRST HOUR brings your IT and operations leads into one short conversation. Walk through a fictional situation, sketch a contact map, and identify the questions you still need to answer.

Proposed format: 30 minutes, with a facilitator.

Call to action: Explore the workshop.

LANDING PAGE / SAMPLE COPY

Practice the conversation
before you need it.

A facilitated discussion for nonprofit operations and IT teams.

  1. Work through a fictional incident prompt.
  2. Discuss who needs information and who makes the next decision.
  3. Leave with a draft contact map and open questions.

Bring the people responsible for IT and day-to-day operations. No technical demonstration is involved.

Reserve a workshop place

Example CTA only. No registration is collected on this portfolio page.

EMAIL / SAMPLE COPY

Thirty minutes to ask
“Who calls whom?”

Subject: Put your incident contact plan to the test

A plan is easier to discuss before it is urgent. Invite your IT and operations leads to FIRST HOUR, a short, facilitated conversation about the decisions that follow a suspected incident.

We will use a fictional situation to map the first contacts, decision owners, and unanswered questions.

Call to action: Review the agenda and reserve a place.

FACILITATOR LEAVE-BEHIND / SAMPLE

A conversation map
to take back to your team.

  1. Who receives the first report?
  2. Who owns the next decision?
  3. Who needs an update, and from whom?
  4. Which contact details or responsibilities need clarification?
  5. Who will resolve each open question, and by when?

This discussion aid would be reviewed by a qualified incident-response practitioner before use. It does not replace an organization’s response plan.

04 / DELIVERY PLAN

Four weeks, with room to learn.

  1. Week 1Review audience assumptions, facilitator credentials, copy, accessibility, and tracking.
  2. Week 2Publish the invitation and send email to an eligible, opted-in audience.
  3. Week 3Review questions and registration drop-off. Adjust unclear copy.
  4. Week 4Run the proposed workshop, send the contact-map template, and review outcomes.

Marketing owns the message and production. A qualified practitioner reviews the scenario and facilitates the discussion. The sponsor approves the offer, registration process, and follow-up.

05 / MEASUREMENT DESIGN

Targets with a denominator
and a deadline.

Illustrative planning scenario for one four-week campaign. These figures are assumptions for an initial test, not industry benchmarks, forecasts, or achieved results.

Proposed measureIllustrative targetReview point
Registration20 registrations from 200 measured landing-page sessions: 10%End of week 3. Review source mix and form friction.
Attendance12 attendees from 20 registrants: 60%Week 4. Review reminder delivery and scheduling.
Requested follow-up3 requests from 12 attendees: 25%Within seven days of the workshop. Record expressed needs and permission to follow up.

Count registrations and attendees once per person. Keep repeat website sessions separate from people. Record follow-up requests separately from sales-qualified opportunities. With a small sample, use results to improve the next test rather than claim a causal lift.

06 / COMPLETED CONCEPT

A clear offer.
A reviewable campaign.

This portfolio exercise contains a fictional brief, a message map, one typographic key visual, four writing samples, a four-week delivery plan, and a measurement scenario.

The next step would be audience interviews and expert review, followed by a small live test. No workshop has been run and no performance results are claimed for this concept.


See actual weekly performance reporting ↗

Have a similar challenge in mind?

Message me on LinkedIn