Printing: report printing
A broken, manual process turned into an organized print flow. I designed it solo, from brief to go-live, in 5 sprints.
- Role
- Senior Product Designer
- Timeline
- 5 sprints
- Platform
- Web (Desktop)
- Team
- Solo designer · engineering team
Overview
ecoPortal is an incident management platform for companies. Users needed to print reports and the platform had no way to do it. I owned the whole design process, from the first lo-fi prototypes to implementation QA, and shipped a configurable print feature that replaced the browser-shortcut workaround.
The problem
ecoPortal is an incident management platform for companies. Users often needed to export and print incident reports, but the platform couldn't do it. Everyone improvised: screenshots, copying data into other software, or printing with the browser shortcut and no control over layout.
What was missing was printing with a controlled layout. An incident report goes through several sections (General data, Investigation, Witnesses, Evidence, Areas) and has sensitive fields that must be hideable before printing. Some people print for internal records, others for external audits. The feature had to serve both without turning into a document editor.
How do we give people real control over what they print, and how, without complicating a flow that has to be fast and reliable?
Briefing
I started with a structured briefing with the product team and stakeholders. Demand came from two sides: user complaints to support, and the business needing paper reports for audits.
Engineering joined early to map technical constraints and what fit in 5 sprints. Initial scope: print the full incident report, with basic layout settings.
Three questions came out of the briefing and guided the rest of the project:
- What do we do with fields the user doesn't want on paper?
- How much customization makes sense before this becomes a document editor?
- How do we make the printout faithful to the content without depending on browser behavior?
Ideation & brainstorming
With the problem framed, I explored widely before committing to any flow or screen structure. I looked at how Salesforce, ServiceNow and Jira handle printing and export, and studied layout conventions in legal documents and corporate forms.
Four hypotheses came out of this phase and held until the end:
- People need a live preview before printing. The output can't be a surprise.
- Settings live in a fixed side panel, not a modal that hides the content.
- Hiding a field has to be explicit, reversible and visually clear.
- Every edge case needs an empty state: no pages selected, all content hidden, unavailable fields.
I settled on three flows to design: the main flow (choose sections → set layout → preview → print), the redaction flow (choose sensitive fields → confirm → preview updates) and the error flows (empty fields, unavailable sections, permission-locked content).
Lo-fi usability testing
Before going hi-fi, I built lo-fi prototypes to test navigation and friction points, not polish. Five internal users took part, security analysts and compliance managers who represent the feature's real audience. I ran moderated think-aloud sessions.
I tested four things: side panel versus modal, the redaction flow, whether people understood "stages" (the report sections you can pick for printing), and how selecting and deselecting sections worked.
What I found:
- The side panel was understood faster, because people could see the preview and the options at the same time.
- "Redact" didn't make sense without explanation. "Hide from printout" worked much better.
- The Stages component needed clearer states. People couldn't tell at a glance what was selected.
- Users tried clicking individual fields to remove them from the printout. It was out of scope, but it pointed to a real need.
This was the most valuable step of the project. Problems found here only cost flow tweaks. Found in hi-fi or during implementation, they would have been far more expensive.
Flow refinement
With the test results, I revised the flows before hi-fi. Every structural change in this phase came from observed behavior, not assumptions.
What changed
Redaction label: "Redact" became "hide from printout" in the intermediate flows. After aligning with the product team, we went back to a more technical term in hi-fi, which fit the platform's corporate context better.
Stages component: redesigned with three explicit states (checked, unchecked and indeterminate). I reworked the visual hierarchy so it was immediately clear what would and wouldn't be printed.
Side panel confirmed: the structure held up. I regrouped the settings into Page Options (header, page numbers, company logo) and More Options (images at the end, thumbnail size).
Unavailable fields as a priority edge case: fields locked by permissions or business rules needed their own visual state. If they vanished or looked editable, they'd cause confusion or errors in production.
Hi-fi design
With validated flows, I moved to hi-fi on top of ecoPortal's design system, specifying every state, variant and edge case.
The final structure has five areas:
Stages: picks which sections go to print. Each report section can be switched on or off, with checked, unchecked and indeterminate states. People print only what matters for their context.
Page Options: toggles for the standard header (SH), page numbers and the company logo.
More Options: header variants, page numbers, images at the end, thumbnail size and company logo, all with live preview.
Security / Redacted Information: a "Redacted" badge marks hidden fields or sections, and the preview shows in real time what will end up on paper.
Misc: supporting components such as the empty state (web and mobile), mailbox field, disabled fields, unavailable fields with their own visual feedback, and the React-inside-Angular integration spec for engineering.
Design decisions
The two-panel layout, with preview on the left and settings on the right, keeps the output in view while people configure it. Page Options shows the essentials. More Options starts collapsed, so people who just want to print fast aren't overloaded. All visuals come from ecoPortal's tokens (Desktop/Mobile, ecoPortal Pro), which keeps the feature consistent with the rest of the product.
Handoff & design QA
My work didn't end at handoff. I followed the whole implementation and owned design QA.
The handoff included full Figma documentation (spacing, color tokens, states and behaviors), interaction specs for the three trickiest flows (redaction, stage selection and preview updates) and two walkthrough sessions with engineering.
During QA I checked every sprint delivery against the design and logged issues with the PO. The main ones:
- Settings panel padding off spec
- Redacted state feedback different from the design
- Preview on smaller screens needing responsive fixes
- Hover states on the Stages component missing
Everything was fixed before go-live. Treating QA as a formal, documented step rather than an informal check kept the delivery faithful to the design and made engineering pay closer attention to detail from the start.
Results & learnings
The feature shipped very close to the design. Two meetings a week were enough to keep everyone aligned without adding overhead. Organizing the Figma file by flow (Stages, Page Options, More Options, Security and Misc as separate sections) sped up handoff and QA a lot, because engineering knew exactly where each spec lived.
What I'd do differently:
- Test with external users. The lo-fi sessions only had internal participants, and a round with ecoPortal customers would probably have shown uses we didn't anticipate.
- Check responsiveness before handoff. The small-screen fixes found in QA were avoidable.
- Map edge cases earlier. Some scenarios, like permission-locked fields and image-heavy reports, only showed up during implementation.
Next steps for the product: look at post-launch usage to see which settings people actually use, build a native mobile version, and merge printing and PDF export into one flow.