I lead discovery and end-to-end product design for EHW+, turning energy and water data into clearer cross-platform decisions while keeping confidential product evidence private.
System viewConceptual visualization, not production UI
RoleLead Product Design
ScopeDiscovery to delivery
SurfacesMobile, tablet, web
FocusReusable behavior
01 / Public context
One view across energy and water
The public EHW+ product helps households record electricity, heating and water meter readings, understand likely costs and use the experience across smartphone, tablet and PC. Optional synchronization connects those surfaces. My case focuses on how I structure product work around that public context, not on disclosing internal product plans.
Input
Meter readings
Different household resources need a clear, repeatable way to capture and review readings.
Interpretation
Consumption and cost
Recorded data becomes useful when the product helps people understand what it means.
Future view
Forecasts
Projected consumption and cost can turn historical tracking into an actionable planning tool.
Continuity
Cross-device access
Mobile and web contexts need consistent behavior while respecting user choice around synchronization.
Public product context is available at ehwplus.de ↗. Internal metrics and confidential artifacts are not reproduced here.
02 / Responsibility
From underdefined need to validated product behavior
I create structure when the initial question is broader than a feature definition. Research, usability evidence, workflow analysis and product data establish what needs to change. Requirements and prototypes then make the proposed behavior testable before it becomes a shared component or implementation decision.
01Frame the problem
02Research the workflow
03Model requirements
04Prototype and validate
05Systemize and implement
Discovery
Evidence before scope
User research, usability testing, workflow analysis and product data challenge assumptions before solution work.
Definition
Requirements and priorities
Findings become explicit product requirements, boundaries and decisions that a team can evaluate.
Validation
Interactive prototypes
Wireframes and prototypes test information order, behavior and comprehension before implementation.
Scale
Reusable foundations
Validated flows become reusable cross-platform components and design-system behavior.
Explore the full decision traceEvidence, model, validation and product rule03 / Decision trace
Show the reasoning without exposing the client
Evidence
A usability signal, workflow observation or product-data pattern indicates where the current model needs review.
System model
Actors, information, states, device context and dependencies make the wider problem visible.
Choice
Alternative behaviors are compared through user value, business relevance, feasibility and consistency.
Validation
The critical path is prototyped and tested before the team commits to detailed implementation.
Product rule
The chosen behavior becomes a requirement, reusable pattern and implementation reference.
This abstracted chain communicates the ownership and systems thinking behind the work without revealing participant data, proprietary findings or unreleased product direction.
04 / Collaboration
Carry decisions through implementation
The work continues after validation. I partner with founders, product and engineering to refine technical constraints, preserve the intended behavior through implementation and keep cross-platform patterns coherent as the product evolves.
The evidence shown here proves responsibility, not adoption attribution.
EHW+ has a public product and active user community, but no company-level usage, revenue or adoption number is presented as my personal design impact. The supported claim is end-to-end ownership from discovery through a scalable cross-platform foundation.
