Independent designer · Creative problem solver

Designing with purpose.
Building with intent.

I'm Dalton Crowell, a graphic design graduate interested in the intersection of user experience, visual identity, and thoughtful project delivery. I bring a visual-design foundation, client-service experience, and a practical approach to solving problems.

BFA · Graphic DesignUX/UIBrand identityProject coordination
Portfolio / 2026
DESIGN PRACTICEMake it clear.
Make it matter.
Research · Design · Deliver
00 / Professional experience

Real-world experience.
People, priorities & problem-solving.

Alongside my design education and independent projects, I bring professional experience supporting client relationships, reviewing account information, and managing time-sensitive requests.

Professional experienceClient operations · Account analysis

Enterprise Strategic Solution Specialist

Waystar

Served as a point of contact between Waystar and key clients and partners. Responded to phone and email inquiries, reviewed account information, and managed competing priorities while working to meet urgent deadlines.

Core responsibilities
  • Client & partner communication: handled incoming phone and email inquiries as a point of contact between Waystar and key accounts.
  • Account review: Reviewed account information to help identify client needs, questions, and items requiring attention.
  • Relationship management: Communicated with clients and partners clearly and professionally, including high-profile accounts.
  • Prioritization: Organized competing requests and focused on urgent matters to support timely responses.
Stakeholder communicationAccount analysisClient relationship managementPrioritizationDeadline managementProblem-solving
How this experience strengthens my design work

Working directly with clients strengthened my ability to listen, clarify requests, communicate clearly, and prioritize competing needs. I bring those habits to design work, collaboration, and project delivery.

01 / The designer

Good design solves.
Great design connects.

I bring a visual-design foundation to digital experiences and creative workflows—balancing how something looks, how it works, and how it gets delivered.

About me

Visual thinking.
Practical execution.

I hold a Bachelor of Fine Arts in Graphic Design. My approach combines visual storytelling, clear communication, curiosity, and organized execution. I enjoy moving from an early idea to a considered design system and a well-prepared handoff.

I'm interested in opportunities across UX/UI design, graphic design, and creative project coordination where I can keep learning and contribute to meaningful work.

How I work

From the first question
to the final handoff.

I start by clarifying the problem and audience. I explore options, make the structure understandable, refine the visual system, and check the details before delivery.

01Understand
02Explore
03Deliver
02 / Selected work

Five ways to
make an impact.

These projects include academic work, independent concepts, and simulated exercises. Each case study identifies its context and distinguishes completed work from proposed next steps.

01 / UX & website redesign
New Albanian
Brewing Co.
CRAFT
BEER
INDIANA
Our storyBeerVisitShop
UX/UI · Web designAcademic project · 2023

New Albanian Brewing Company

A brewery website redesign exploring clearer navigation, stronger storytelling, and a more connected path to beer, location, and visitor information.

Explore case study ↗
Information architectureWeb redesignVisual hierarchy
02 / UX & digital experience
Fistful
of Ale.
FISTFUL OF ALE
UX/UI · Site consolidationAcademic project · 2023

Fistful of Ale

A digital experience redesign focused on bringing related web destinations into a more consistent, recognizable experience.

Explore case study ↗
Content structureNavigationVisual consistency
03 / UX & product design
Find your
space.
SAFE PARK / EXPLORE
Parking near
your destination
UX/UI · ResearchConcept case study

SafePark

A mobile-first parking discovery concept focused on making options easier to compare and understand.

Explore case study ↗
Research planUser flowsInterface design
04 / Brand & graphic design
A guide to places with a point of view.
LOCAL
FINDS
/ 01 /
Branding · Art directionFictional brand

Fieldnote

A flexible identity for a neighborhood discovery brand, built around editorial clarity and local character.

Explore case study ↗
Brand strategyIdentity systemCampaign assets
05 / Project management
Make the
work work.
CAMPAIGN BOARD
Creative brief ✓
Design production ↗
Review & approval ○
Final delivery ○
Planning · DeliverySimulated project

Launch Studio

A practical delivery framework for coordinating a multi-channel creative campaign from kickoff to handoff.

Explore case study ↗
Project charterTimelineRisk planning
Case study 01 / UX & website redesign · 2023

New Albanian
Brewing Company

A website redesign exploration for a brewery brand—bringing its story, beer, and visitor information into a clearer digital experience.

PROJECT TYPESelf-initiated academic UX / website redesign
YEAR2023 · Class presentation
MY ROLEIndependent concept development and visual design
DESIGN FOCUSInformation architecture · Navigation · Responsive web
DELIVERABLESOriginal wireframe · Desktop and mobile screens · Page concepts
PROJECT ORIGINInspired by discovering the businesses at a campus food-truck event
CORE OPPORTUNITYMake key brewery information easier to find and explore
PROJECT SCOPEA proposed redesign concept; not commissioned or launched
Where the project started

A memorable campus experience exposed a digital opportunity

New Albanian Brewing Company and Fistful of Ale visited my campus with their food trucks. I enjoyed the food and drinks, but I also noticed the brands through a designer’s lens. When I later explored their websites, the contrast stood out: the in-person experience felt inviting, while the websites felt dated and difficult to navigate—even to someone who is comfortable with technology.

I chose the businesses for an independent class project and presented a redesign concept to my class. My goal for New Albanian was to explore how the website could make the brewery’s story, food and drink offerings, promotions, gallery content, and practical visitor information easier to discover.

01 / Organize

Group information around common visitor needs: learn about the brewery, explore what is offered, browse imagery, and plan a visit.

02 / Clarify

Use the original wireframe to explore page hierarchy and navigation before developing the desktop and mobile screen concepts.

03 / Adapt

Carry the content structure across screen sizes so the experience remains understandable on both desktop and mobile.

New Albanian Brewing CompanyWebsite redesign concept / 2023
A better way to explore

Good beer.
Good people.
Good times.

Concept direction: make the brewery's identity and key visitor paths easier to discover, while giving its beer and story room to speak.

NEW ALBANIANBeer   Story   Visit   Shop
Find your
next favorite.
Explore the brewery

The challenge

The redesign explored how a brewery website could help visitors understand the brand and quickly reach the information they came for. Beer discovery, the brewery story, visiting details, and related destinations all compete for attention if the site structure is not clear.

Design objective

Create a more coherent website experience with a recognizable visual voice, an understandable navigation system, and clear routes to the brewery's most important content.

My design focus

  • Establish a clear hierarchy between brand storytelling and practical visitor information.
  • Make the primary navigation easier to scan and understand.
  • Give beer and brewery content a consistent presentation pattern.
  • Use typography, color, imagery, and spacing to make the experience feel like one brand.

Key UX considerations

  • Can a first-time visitor quickly find where to go and what to expect?
  • Can someone interested in the beer browse without getting lost in brand content?
  • Do page layouts establish a predictable rhythm across different content types?
  • Does the design remain readable and usable on smaller screens?

Information architecture

The concept organizes the experience around four visitor needs: learning about the brewery, exploring its beer, finding visit information, and reaching online or shop-related content. The proposed structure is presented as a design direction rather than a record of a launched website.

Visual direction

The portfolio presentation uses a warm, brewery-inspired palette, editorial serif display type, and restrained navigation details. The mockup is a newly composed presentation visual—not a claim that this exact screen was part of the original deliverable.

What I would validate next

  • Ask representative visitors to find hours, directions, and other visit details.
  • Ask beer-focused visitors to locate a specific beer and understand its description.
  • Test navigation labels and mobile page hierarchy with realistic tasks.
  • Review contrast, keyboard focus, tap targets, and responsive behavior.

No usability-test results or post-launch analytics are claimed in this refreshed presentation.

UX design rationale

Make the visitor's next step obvious

  • Group navigation around visitor intent: learn the story, explore food and drink, browse the gallery, and take an ordering or visit-related action.
  • Keep a consistent header and navigation model across pages so visitors always know where they are and how to move elsewhere.
  • Use a strong content hierarchy: one primary message, supporting detail, then a clear next action. Avoid placing multiple competing calls to action at the same visual level.
  • Design mobile layouts around scanability: concise headings, readable body text, appropriately sized tap targets, and a clear path to the menu or order information.
  • Treat image-heavy sections as content, not decoration: add meaningful alternative text and ensure text remains readable when layered over photography.

The original evaluation sheet is shown as a project artifact. It is not used here to claim validated research findings or usability outcomes.

Case study 02 / UX & digital experience · 2023

Fistful of Ale

A digital redesign concept exploring how related brand destinations could feel more connected through clearer navigation and a consistent visual system.

PROJECT TYPESelf-initiated academic UX / digital experience redesign
YEAR2023 · Class presentation
MY ROLEIndependent concept development and visual design
DESIGN FOCUSContent consolidation · Navigation · Responsive design
DELIVERABLESOriginal wireframe · Desktop and mobile screens · Membership and food/beverage page concepts
PROJECT ORIGINInspired by discovering Fistful of Ale at a campus food-truck event
CORE OPPORTUNITYCreate a more connected, recognizable experience across related content
PROJECT SCOPEA proposed redesign concept; not commissioned or launched
The Fistful of Ale design opportunity

Make connected content feel like one coherent experience

The same campus event inspired both redesign concepts, but each project had a different focus. For Fistful of Ale, I explored how related destinations and content could feel more connected through a shared structure and a more consistent visual language.

For this class project, I explored how visitors might move between brand information and practical content, including membership, food and beverage information, events, catering, and bookings. I developed the concept independently and presented it to my class; the work was not commissioned by or launched for the business.

01 / Connect

Use a shared navigation approach and recognizable page patterns to make relationships between destinations easier to understand.

02 / Prioritize

Give practical visitor tasks and key content—such as membership, events, catering, and bookings—a clearer place in the experience.

03 / Carry through

Apply a consistent visual hierarchy across desktop and mobile concepts while keeping the brand’s own character.

Fistful of AleDigital experience concept / 2023
One brand. One clear experience.

A little more
character.

A refreshed visual direction designed to make the brand feel connected across its digital touchpoints.

FISTFUL OF ALEDiscover   About   Find us
Raise a glass
to good taste.
Explore the story

The challenge

The project explored a familiar digital-brand problem: when related parts of a brand live across separate websites or experiences, users can encounter inconsistent navigation, visual language, and content structure. The redesign aimed to make those destinations feel more connected.

Design objective

Bring the experience under a clearer visual and navigational system, so visitors can understand the brand, explore its content, and move between related information without feeling as though they have left the same experience.

My design focus

  • Identify shared content and navigation needs across the related destinations.
  • Define a consistent visual hierarchy for headings, imagery, navigation, and calls to action.
  • Reduce competing visual patterns and make page relationships easier to understand.
  • Keep the brand personality distinctive without sacrificing usability.

Structure & consistency

  • Use a common navigation and page framework.
  • Make the primary content and next steps clear on each page.
  • Use repeatable components for related content.
  • Keep typography, color, and image treatment consistent across the experience.

Why consolidation matters

A connected design system can reduce the cognitive work of learning multiple navigation patterns. It also gives the brand a more coherent presentation. The actual impact would need to be evaluated through user testing and, if launched, analytics.

Visual direction

The case-study presentation uses a warm, craft-inspired palette and editorial typography. The featured visual is a portfolio mockup created to present the concept, not a screenshot of a live website.

What I would validate next

  • Test whether visitors understand the main navigation and how the destinations relate.
  • Give users common tasks and observe whether they can move between content areas without backtracking.
  • Check responsive behavior and accessibility across the shared page system.
  • Compare the consolidated structure with the original experience to identify what became clearer and what may have been lost.

No completed usability testing, live consolidation, or measured performance improvements are claimed here.

UX design rationale

A clearer family of destinations

  • Unify the primary navigation so visitors can recognize the shared Fistful family and move between related destinations without relearning the interface.
  • Use a repeatable page structure: clear page title, one primary action, supporting content, and a predictable footer or next step.
  • Give high-intent tasks—events, catering, contact, and online ordering—direct labels rather than burying them in decorative content.
  • On mobile, prioritize a compact menu, readable content blocks, and thumb-friendly calls to action; keep image overlays legible against busy photography.

These recommendations reflect my design interpretation of the supplied sketches and screens; they are not usability-test findings or measured outcomes.

Case study 03 / UX & product design

SafePark

Helping drivers make a more informed parking choice by bringing the details that shape a decision into one clear experience.

The challenge

Parking decisions can involve several variables: location, price, time window, entry instructions, restrictions, and whether a space can be reserved. The concept explores how to make those variables easier to scan before a driver commits.

Design question

How might we help a driver compare parking options with enough clarity to choose confidently—without implying that availability data is live when it may not be?

Desk research

  • ParkMobile publicly describes both pay-for-parking and advance reservation flows, including zone, time, vehicle, and payment steps.
  • SpotHero describes search and comparison across hourly, monthly, airport, and event parking, followed by prepaid reservation and arrival instructions.
  • These patterns suggest the experience must distinguish “pay for a parking session” from “reserve a specific facility/time window.”

Desk research references: ParkMobile's public parking-payment information and SpotHero's public FAQ. This review informed the concept; it was not primary user research.

Product principles

  • Clarity: show price, distance, hours, and restrictions in consistent positions.
  • Trust: label availability as live, estimated, or unverified; show update time where available.
  • Choice: support map and list views so location is not the only way to compare.
  • Access: make key details available as text, not only map symbols.

Proposed core screens

SAFE PARK / 01 — SEARCH

Where are you headed?

Destination Downtown / enter address
Arrival Today · 6:30 PM
Duration 2 hours
Find parking
SAFE PARK / 02 — RESULTS

Options near you

Market Street Garage$12 · 4 min walk · Hours shown
Central Lot$9 · 7 min walk · Restrictions apply
SAFE PARK / 03 — DETAIL

Know before you go.

Market Street GarageExample concept listing
Price $12 estimated total
Walk 4 minutes
Availability Not verified in prototype
View directions

Research plan

Proposed next step: interview drivers who have recently parked in unfamiliar areas. Ask about their last parking decision, the information they checked, and what created uncertainty. Follow with task-based sessions using the prototype.

Success measures

  • Can participants identify the total price and restrictions?
  • Can they compare two options and explain their choice?
  • Do they understand whether availability is confirmed?
  • Where do they hesitate, backtrack, or misinterpret labels?

How I translated the problem into a product structure

Working assumption: the primary user is a driver who needs to park somewhere unfamiliar and wants to understand cost, walking distance, restrictions, and confidence in the listing before committing. This is a proto-persona hypothesis—not a validated research finding.

01 / FINDEnter a destination, arrival time, and expected stay.
02 / COMPAREScan price, walk time, facility type, restrictions, and data confidence.
03 / DECIDEReview entry details and choose directions or a verified reservation path.
Destination→Search criteria→Map + list results→Option details→Directions / booking

Information hierarchy

  1. Decision essentials first: total price, walking time, and restrictions.
  2. Trust context next: source, last-updated timestamp, and availability confidence.
  3. Supporting detail: height limits, payment rules, entrance location, and cancellation terms where known.

Design iteration rationale

  • Search: separate destination, arrival, and duration so the inputs are easy to review.
  • Results: pair a map with a scannable list; do not force map-only discovery.
  • Detail: move restrictions and price breakdown above the primary action.
  • Trust: use plain-language confidence labels rather than implying real-time availability.

Validation plan: what I would test next

Proposed validation: recruit five to seven people who have parked in an unfamiliar area within the past three months. Ask them to describe their last parking decision before showing the concept.

Usability taskWhat I would observePotential signal
Find parking within a stated budget and walking distance.Search completion, backtracking, and filter comprehension.Can the participant identify a suitable option without help?
Compare two facilities and choose one.Whether price, restrictions, and walk time are noticed.Can they explain their choice using the displayed details?
Explain the availability label.Interpretation of “unverified,” “estimated,” and update time.Do they understand what is and is not confirmed?
Locate entry instructions and next steps.Findability of entrance, payment, and directions.Can they describe what happens after selecting an option?
Prototype success criteria (targets, not results): participants should be able to identify the displayed total price and key restriction, compare two options, and accurately explain whether availability is confirmed. Record task completion, critical errors, time-on-task, and confidence rating; revise the interface based on observed friction.

Interview prompts

  • Tell me about the last time you parked somewhere unfamiliar.
  • What did you need to know before choosing?
  • What information was difficult to find or trust?
  • What would make you abandon an option?
  • How do you interpret the difference between estimated and confirmed availability?

What I would document

  • Participant context without unnecessary personal data.
  • Direct observations separated from interpretation.
  • Repeated patterns and meaningful exceptions.
  • Severity and frequency of usability issues.
  • Design changes linked to observed evidence.
Key design decision: Never use a green “available” badge unless a reliable live data source supports it. In this concept, availability is explicitly marked as unverified.
Case study 04 / Brand & graphic design

Fieldnote

A visual identity concept for a neighborhood discovery guide that celebrates independent places through useful information and an editorial point of view.

The brief

Create a recognizable identity for a digital guide to independent shops, makers, cafés, and neighborhood experiences. The system must feel warm and distinctive while remaining readable and adaptable across social, print, and web.

Audience hypothesis

People who like discovering local businesses may respond to recommendations that feel curated and specific rather than generic directory listings. This is a strategic hypothesis to validate through interviews and concept feedback.

A neighborhood field guide

fieldnote.

Find the places that make a neighborhood feel like itself.

CURIOUS
BY NATURE
EST. CONCEPT

Identity system

  • Wordmark: lowercase editorial lettering for approachability and easy recognition.
  • Color: warm paper, deep ink, and muted field green for a collected, tactile feel.
  • Typography: expressive display type balanced with a highly legible sans serif.
  • Graphic language: stamps, location notes, grids, numbering, and documentary-style imagery.
Paper / #D7D0BF
Ink / #20231F
Field / #54785C
Signal / #D7A35C

Applications & quality checks

  • Primary and compact logo lockups.
  • Social post and story templates.
  • Digital place card and landing-page hero.
  • One-page mini brand guide.
  • Test logo legibility at avatar size and in monochrome.
  • Check contrast and type sizes for accessibility.

Brand positioning

Positioning statement: For curious locals and visitors who want a more thoughtful way to discover independent places, Fieldnote is a neighborhood guide that favors useful context and a human editorial voice over endless generic listings.

Personality: curious, grounded, observant, welcoming. Avoid overly precious language or a luxury tone that could make local discovery feel exclusive.

Message system

  • Primary promise: Find the places that make a neighborhood feel like itself.
  • Supporting idea: Short, specific notes help people understand why a place is worth visiting.
  • Voice: concise, descriptive, warm, and never overclaiming.
  • Content rule: distinguish editorial recommendation from factual business details.

Identity in use

fieldnote.Neighborhood guide / 01
LOCAL
NOTES
Places worth
the detour.
Social campaign tile
FN / 01
Take the
scenic route.
Editorial feature cover
FIELD
GUIDE

Design system rules

  • Use the wordmark with generous clear space; never stretch or add effects.
  • Use paper and ink as the default foundation; field green is an accent, not a body-text color on dark surfaces.
  • Use display typography for short headlines only; body copy stays highly legible.
  • Use stamps, issue numbers, and location notes as supporting devices—not decoration on every component.
  • Maintain contrast and test the identity at small avatar and mobile sizes.

Production checklist

  • Primary and compact wordmark exports.
  • Light, dark, and one-color logo versions.
  • Color and typography specification sheet.
  • Social feed tile, story frame, and editorial cover.
  • Digital place-card template with clear content hierarchy.
  • Exported assets named consistently and packaged with usage notes.

How I would validate the identity

Proposed validation: show two or three identity directions to a small group of intended users. Ask what kind of service they expect, what feels memorable, and what is difficult to read. Then test the selected direction in realistic contexts, including a small social avatar, a longer place description, and a printed guide. No preference testing has been conducted.

What makes the concept coherent: The visual system borrows from field journals and editorial guides, but the layouts remain modular so a short business description, a long feature, and a social tile can all feel like the same brand.
Case study 05 / Project management

Launch Studio

A lightweight operating model for delivering a coordinated creative campaign with clear ownership, review points, and a dependable handoff.

The scenario

A small organization needs a coordinated campaign across a digital flyer, social feed creative, story format, and landing-page update. The delivery challenge is to keep the message and visual identity consistent while managing dependencies, reviews, and deadline risk.

Operating principles

  • Define the deliverables and “done” criteria before production.
  • Assign one accountable approver.
  • Consolidate feedback into clear revision rounds.
  • Make schedule impact visible when scope changes.

Illustrative campaign board

TO DO

Confirm campaign briefOwner: Project lead
Collect approved assetsOwner: Content

IN PROGRESS

Build master visual directionOwner: Designer
Adapt social formatsOwner: Designer

REVIEW / DONE

Copy accuracy checkOwner: Content lead
Final export & handoffOwner: Project lead

10-day delivery plan

Days 1–2
Days 3–4
Days 5–6
Days 7–8
Days 9–10

Kickoff → research & direction → design production → review & revisions → QA and delivery.

Risk & response

  • Late feedback: single approver and clear review deadline.
  • Missing assets: audit at kickoff and agree on fallback options.
  • Scope creep: log change, owner, and schedule impact before accepting.
  • Incorrect copy: assign a content owner to verify factual details.
  • Export errors: preview files at target dimensions and on-device.

Scope and deliverables

In scope: one campaign concept, one master visual direction, one digital flyer, three social feed adaptations, two story frames, and a landing-page hero update.

Out of scope: paid media buying, website development, photography production, and ongoing community management. These exclusions protect the schedule and clarify what the handoff does not include.

Definition of done

  • All agreed formats are exported to approved dimensions.
  • Copy, dates, links, and calls to action are checked by the content owner.
  • One accountable approver has signed off.
  • Files use agreed naming and folder structure.
  • Source files and usage notes are included in handoff.

Responsibility matrix (illustrative)

WorkstreamProject leadDesignerContent ownerApprover
Brief and scopeResponsibleConsultedConsultedAccountable
Visual directionConsultedResponsibleConsultedAccountable
Copy and factual checksInformedConsultedResponsibleAccountable
Final export and handoffResponsibleResponsibleConsultedAccountable

One person may hold multiple roles in a small team; the key is to make accountability explicit.

Communication rhythm

  • Kickoff: confirm objective, audience, scope, owners, dependencies, and approval path.
  • Daily async update: completed, next, blocked, and decisions needed.
  • Midpoint review: review the master direction before adapting formats.
  • Approval checkpoint: consolidate feedback into one prioritized list.
  • Handoff: confirm file access, formats, version, and receiving owner.

Change-control example

If a new deliverable is requested after design production begins, log the request, reason, owner, effort, and schedule impact. The approver then chooses to add time, remove another deliverable, or defer the request to a later phase. This prevents hidden scope growth.

Milestone gates

GATE 01 / BRIEFScope, audience, message, owners, and success criteria approved.
GATE 02 / DIRECTIONMaster concept and content hierarchy approved before adaptations.
GATE 03 / DELIVERYQA complete, formats checked, approval recorded, handoff accepted.
How I would measure delivery quality: on-time handoff against the agreed schedule, number of unresolved approval items at delivery, completeness of required formats, and whether the receiving owner can locate and use the final files.
03 / Capabilities

Creative range.
Structured thinking.

A foundation in visual communication, supported by hands-on practice with UX methods and project planning.

UX / UI DesignProblem framing, user flows, wireframing, interface hierarchy, prototyping, usability planning.
Graphic DesignVisual identity, typography, layout, campaign design, art direction, digital assets.
Project CoordinationScope, milestones, dependencies, stakeholder communication, review cycles, handoff.
Research & StrategyCompetitive review, interview planning, synthesis frameworks, design rationale.
Visual SystemsConsistency, reusable components, brand rules, responsive design thinking.
Quality & AccessibilityContent clarity, contrast awareness, keyboard and focus considerations, responsive checks.
Tools & software

The tools behind the work.

Tools I use across visual design, prototyping, website building, and collaboration.

PhotoshopAdobe
IllustratorAdobe
InDesignAdobe
Premiere ProAdobe
After EffectsAdobe
LightroomAdobe
FigmaDesign
SketchDesign
CanvaDesign
WixWeb
HTMLDevelopment
CSSDevelopment
WordMicrosoft
TeamsMicrosoft
PowerPointMicrosoft
ExcelMicrosoft
04 / Start a conversation

Have a good challenge?
Let's make it clear.

I'm open to opportunities in UX/UI design, graphic design, and creative project coordination.

Prefer a document? Download a PDF version of my portfolio to review or share.