Design for B2B products
B2B Produkte
From structure to implementation: system logic, clear flows and scalable interfaces.
Gremminger
Product Systems
Structure before UI.
Models core entities, rules, and states as the foundation for consistent workflows and reliable implementation. Reduces interpretation gaps between domain and engineering and creates system logic that scales with new features.
Journeys that lead
Builds clear information architecture and flow logic across key journeys. Focuses on dependencies, state transitions, and decision paths so users can move through complex processes with confidence.
Make complexity operable.
Designs interfaces for data-intensive products (tables, filters, detail views, configuration) using consistent interaction patterns. Improves orientation, reduces errors, and supports reliable decision-making in operational workflows.
Test early. Decide cleanly.
Creates clickable prototypes to validate flow logic, information hierarchy, and interaction behavior before development commits. Enables faster alignment across product and engineering and increases delivery confidence in high-change phases.
Remove friction fast.
Provides structured analysis of existing UX across critical journeys, system logic, and UI patterns. Delivers a prioritized improvement backlog that reduces inconsistencies and stabilizes scaling across modules.
BI Dashboards
Decision-ready dashboards.
Designs Power BI dashboards for readability, orientation, and consistent interaction patterns. Helps operational users make faster decisions and reduces misinterpretation through clear visual hierarchy.
Make KPI logic visible.
Translates complex metrics into understandable visuals and narratives. Focuses on comparability, context, and clear statements so KPIs are interpreted confidently – not just displayed.
Structure for drilldowns.
Builds scalable dashboard architecture (pages, navigation, drilldown logic) across multiple audiences and use cases. Improves findability, lowers cognitive load, and prevents reporting sprawl.
Low-friction data work.
Standardizes patterns for filters, tables, detail views, and states (empty/loading/error). Makes recurring analyses faster and more consistent in data-heavy workflows.
Dashboards people actually use.
Runs qualitative tests and structured task analysis to uncover comprehension issues, misreads, and friction. Produces concrete improvements to structure, visuals, and interactions.
Standards over style mix.
Establishes visual standards for consistency, comparability, and fast readability. Applies IBCS principles where management reporting conventions and decision clarity are critical.
Design Systems
One system. Many surfaces.
Establishes a token foundation (type, spacing, color, states) that keeps design and engineering in sync. Enables scalable UI decisions and reduces drift across teams and products.
Reuse beats rework.
Defines modular components and patterns for recurring UI problems (navigation, forms, tables, filters, empty/loading/error states). Speeds up delivery while maintaining consistency as the product expands.
States are part of design.
Systematizes states, variants, and responsive behavior as explicit rules. Supports reliable implementation and prevents fragmentation as roles, contexts, and features multiply.
Scale through templates.
Builds template and module libraries for pages, views, and recurring layouts. Ideal for products with many data views or product-facing web areas where speed and consistency matter.
Usable, not just pretty.
Documents principles, usage rules, do’s/don’ts, and examples so the system works in day-to-day delivery. Reduces alignment overhead and improves adoption across teams and partners.
Engineering-aligned by default.
Defines handover formats, specs, and governance mechanisms so the system stays consistent over time. Supports collaboration with tech leads and prevents system decay under feature pressure.
Design Systems
Web as interface, not decoration.
Builds product-facing SaaS websites as scalable systems: information architecture, modular sections, and clear conversion flows (demo/contact). Includes consistent visuals, CMS and clean handover – or Webflow delivery when it’s part of the product experience.
A story that converts.
Structures and designs decks with clear argumentation, consistent visual language, and reliable number communication. Works best as an add-on to product, BI, or go-to-market work so messaging and visuals come from one system.
Clarity in days, not weeks.
Provides a focused review of critical journeys with clear findings and prioritized fixes. Ideal ahead of releases, pitches, or when teams need fast direction without a full research program.