Systems Thinking // Interaction Design // Adobe Firefly Unified Prompting

Prompting Patterns for Adobe Firefly

Unifying Firefly's separately built generation tools with a prompting pattern that grows with the user, from beginner to expert alike.

CONTEXT

Coursework

TIMELINE

2025 / 5 weeks

TEAM

3 Undergraduate Students

CONTRIBUTIONS

Competitor Analysis / User Interviews / Research Synthesis / Ideation / Lo-fi Wireframe

01 / CONTEXT

Firefly is Adobe’s generative AI platform for creating images, graphics, video, and audio. Over time, each workflow (Text to Image, Text to Video, Generate Sound Effects) was built independently, resulting in inconsistent prompting experiences across the product.

02 / CHALLENGE

Each workflow had grown its own prompting conventions. As Firefly expands into mutlimodal prompting and third-party models, these inconsistencies will only become harder for users to navigate.

Adobe asked our team to step back and look at prompting as a system rather than a widget. The goal wasn’t to add new features, but rather to understand how users actually move through Firefly and how the product could feel like one coherent environment rather than three loosely related tools.

03 / PROCESS

Firefly’s users aren’t a monolith. Some arrive with no generative AI experience at all, others show up with deeply engrained habits from tools like Claude or Chat GPT. It’s not fair to proceed as if all users have the same needs or pain points, so we split them into two groups, each with their own assumptions: Novice and Advanced users.

We also looked outward. If users are already trained by competitors, then Firefly isn’t just teaching prompting, it’s also competing with existing mental models. That raised a simple question: How are other tools doing it?

Our competitor analysis mapped how prompting appears, behaves, and scales across leading generative AI platforms that compete with Adobe. This helped us understand which patterns users already trust, which ones create friction, and where Firefly has room to differentiate.

04 / EVIDENCE

Our research surfaced a theme:

Every user arrives with expectations, based on prior experiences, and Firefly’s inconsistency across workflows broke them.

Beginner

Prompt bar is the whole mental model.

When its location or behavior changed, they lost confidence in what to do next.

“

I wouldn’t know to use the sidebar because it’s not what I’m used to for AI.

Beginner participant

Advanced

Expected use of the properties panel.

The properties panel varied between workflows, so the structure and clarity they expected never arrived.

“

The properties panel reminds me of Photoshop, so I have some idea of what to expect from it.

Advanced participant

All Users

Audio workflow completely broke the pattern.

A new interaction model deviated from what image and video generation had taught.

“

How the f*ck do I do this?

Beginner participant

05 / Solution

Solution aims to create a prompting pattern that:

(A)

scales from beginner to advanced users AND

(B)

maintains a consistent framework between workflows

The solution operates on two main screens, before content generation and after, meant to apply to all workflows.

Before Content Generation

Click to enlarge

Before Content Generation

After Content Generation

Click to enlarge

After Content Generation

Five components carry the pattern:

Prompt Bar

Decision: Center the prompt bar before the first generation, then move it below the content once results appear.

Evidence: Most users went to the prompt bar first, and beginners used it almost exclusively for each generation attempt.

Rationale: Other generative AI tools use this pattern, so it gives new users an interface they already know.

Before Content Generation

After Content Generation

Generate Button

Decision: Keep the existing generate button at the right end of the prompt bar in the same position across all workflows.

Evidence: Users consistently relied on the prompt bar for generation, and none hesitated over how to submit.

Rationale: Fixing the button in the same spot means every workflow ends the same way; A skill learned in one carries to the others.

Property Panel

Decision: Abstract categorized information into icons that expand in place, with descriptions on hover and more tools available on click.

Evidence: Advanced users fluently navigated the property panel, while beginners ignored it, finding it hard to interpret when asked.

Rationale: Icons reduce visual load for beginners and stay familiar to experienced Adobe users.

On hover, each panel icon expands to show its category name and a short description, so beginners can explore and learn what each category does.

On click, each icon expands to reveal the tools grouped under that category. The panel looks and behaves the same in every workflow, while the tools inside it differ to fit each one.

Plus Button/Menu

Decision: Add a plus button to the prompt bar that opens a categorized dropdown of options, which correspond to the icons in the property panel.

Evidence: Beginners gravitated to the prompt bar. Our competitor analysis showed the plus button is a common prompt bar feature, so it is familiar to users of other generative AI tools.

Rationale: Placing the plus menu inside the prompt bar puts options where beginners already work. Its categories correspond to the panel’s icons, so the menu introduces beginners to what the panel offers.

Descriptive Tabs

Decision: Appearing after prompt properties have been configured, tabs display each selected property as a removable tag beneath the prompt bar.

Evidence: Our competitor analysis and user research found that tabs help users avoid memorizing what they’ve selected and show what prompts have in common.

Rationale: Tags keep the current settings visible and one click from removal, so changing a style never requires reopening a panel.

06 / REFLECTION

Recognition

Adobe Senior Staff Designer Troy Church, who set the brief and judged the class submissions, selected our team’s solution as “most likely to work” among all entries.

What the project taught me:

(A)

Consistency is a design decision.

Every Firefly workflow made sense on its own, but the friction appeared when users carried expectations from one workflow to the next. That is why we treated prompting as a system rather than a widget.

(B)

User research changed our direction more than any competitor reference did.

Looking at competing platforms gave us ideas, but watching the users complete tasks in interviews gave us more information on how they interact with the current Firefly interface. This was key to developing our solution.

(C)

Familiarity can be the feature.

Our solution components borrowed from tools users already trusted, whether it be from advanced Adobe platforms like Photoshop to generative AI tools like ChatGPT. The question became where to match user expectations and where Firefly could do better.

What I’d do next:

Our work stopped at low-fidelity wireframes, so the pattern hasn’t been tested with users yet. Next, I would test the prompt bar and plus menu with beginners to see whether the menu actually encourages them to understand what the property panel offers.

I’d want to check in with the same beginner users later, ask them to run similar tasks, and see if they actually use the property panel now. Conversely, I’d be interested to see if advanced users change their habits, too. Are they more reliant on the plus menu now that it is presented as an option?

Keep moving.