ETHAN Design, art direction & emerging technology
Contact ← Lab
← Lab Lab 004 / Internal tools · Workflow design

Communications Hub & Marketing Requests

In-development prototypes · Sample dataDesigned for Power Apps and SharePointLab project, not client work
Marketing Request Center · dashboard, requesting-manager viewPrototype · Sample data · Click to enlarge
Overview

I developed prototypes for a Communications & Public Affairs hub and a connected marketing request system. The hub brings resources, announcements, and team guidance together. The request system explores how staff can submit work and follow it through review and production.

Design focus

The hub gives staff a clear starting point for common tasks. Within the request system, different roles have different responsibilities, and the dashboard brings requests needing a response to the top. Status, ownership, and next steps stay visible alongside the work.

What to look for
  • 01A shared entry point for resources and marketing requests.
  • 02A structured request form and role-specific views.
  • 03Clear separation between work awaiting approval, awaiting a response, and in production.
Category
Internal tools / Workflow design
Platform context
Designed for Power Apps and SharePoint, around an existing Microsoft 365 environment.

01From the hub to a request

Three screens · prototype captures
Step 1 · Entry point

The hub is where staff start.

Brand guidelines, logos and templates, forms, and the team are grouped in one place. The Marketing Request Center sits near the top with the requester's own counts, so submitting work is one step away from finding a logo.

Design prototype. The photo area and logo tile are labelled placeholders. Search, Campaign Calendar, and Reports & Insights are not completed modules.

Hub homepage · 1440 desktopPrototype · Sample data
Step 2 · Structured intake

A request in six short steps.

Request basics, project details, deliverables, timeline and priority, files, then review. The form asks for the department first and suggests an approver from a routing table, so the request reaches the right person without the requester having to know the org chart.

New request · step 1 of 6Prototype · Sample data
Step 3 · Status and ownership

The next action rises to the top.

When marketing has a question, the request moves into a Needs your response band above the table, with who is waiting and a single Respond action. Everything else stays in the list with its status, priority, needed-by date, and marketing owner.

Detail from the dashboard prototype: a Needs your response band containing Store Signage Refresh, University Pkwy, MR-1054, Marketing asked a question, reply to resume work, with a Waiting on Requester status and a Respond link.
Dashboard detail · Needs your responseCrop of the capture above, for legibility

02Current stage

In development

The hub is a design prototype. The marketing request system includes a browser demo and a separate Power Apps code-app candidate. Production connections and deployment are still to be completed.

  • The screens on this page are browser captures of the source prototypes, not deployed Power Apps screens.
  • Names, requests, and counts are fictional sample data.
  • Navigation from the hub into every module is not built; several modules are placeholders.
{{ lightboxImage }}
{{ lightboxLabel }}