Telefónica.

Facilitating design sprints and digital transformation conversations for a large telecommunications environment, translating service complexity into shared maps, product concepts, prototypes, and alignment artifacts.

Helping transformation teams move from ambition to shared direction.

The work lived in the space between business goals, customer journeys, internal operations, service dependencies, and technology constraints. The first need was not a final interface. It was clarity.

From complex service conversations to tangible product concepts.

Large organizations often have many valid perspectives competing at the same time. The challenge was to create enough structure for teams to align, make decisions, and see what a future product or service experience could become.

Sprint-led clarity.

Add image:
sanitized design sprint board, workshop canvas, journey map, opportunity map, or service ecosystem artifact.

Image row 01 Recommended: workshop or discovery artifact with confidential details removed

Process.

A simplified view of the work: frame the transformation space, facilitate design sprints, prototype possible futures, and leave teams with usable material for next decisions.

01
Frame the service system before jumping into solutions.

The work started by making the transformation context visible: who was involved, what the business wanted to change, where users experienced friction, and which internal systems shaped the service.

The goal was to create a shared view of the problem space before the team started producing ideas, screens, or isolated feature concepts.

Problem framingService mappingStakeholder inputSystems thinking
- Mapped objectives, users, teams, moments, and service dependencies.
- Translated broad transformation goals into designable opportunity areas.
- Identified assumptions and unresolved questions before ideation.
02
Use design sprints to turn discussion into decisions.

Design sprint activities helped compress exploration into a productive rhythm: map, sketch, decide, prototype, and learn. The format made abstract transformation language easier to convert into concrete product and service choices.

Design sprintFacilitationCo-creationPrioritization
- Prepared and facilitated structured workshop sessions with cross-functional participants.
- Created canvases and exercises that forced alignment around the most relevant questions.
- Helped teams compare options through impact, effort, confidence, and learning value.
03
Prototype a future state that could be critiqued safely.

Prototypes and product narratives made the proposed direction tangible enough to evaluate, challenge, and communicate, without needing to expose sensitive business details or overcommit to implementation.

Rapid prototypingProduct narrativeValidationHandoff
- Built interface concepts, flow sketches, and product scenarios to support discussion.
- Used prototypes as thinking tools to reveal gaps, trade-offs, and dependencies.
- Prepared material that teams could reuse for internal storytelling and continuation.

Add image:
sanitized prototype screens, concept flow, final presentation board, or recreated UI with dummy content.

Image row 02 Recommended: abstracted UI composition, concept flow, or before/after service scenario

From workshop energy to product direction.

I supported transformation work by helping teams move from dispersed conversations into visible artifacts: maps, opportunity areas, sprint decisions, prototypes, and next-step recommendations.

The main value was alignment. The process created a common language between business, product, design, and technology stakeholders so the work could continue beyond the sprint.

Design Sprints

Workshop Facilitation

Service Mapping

Opportunity Framing

Prototype Scenarios

Stakeholder Alignment

Handoff Material

Transformation Clarity

facilitation

Decisions made visible. Workshop / sprint board

Design workshops as alignment infrastructure.

Workshops helped teams move from loose opinions to structured decisions, shared maps, prioritized questions, and visible assumptions.

service design

One service, many actors. Journey / ecosystem map

Making the service ecosystem easier to understand.

Maps and synthesis artifacts connected customer moments with internal teams, operational dependencies, business rules, and technology constraints.

prototype

Strategy you can click. Prototype / scenario

Using prototypes to make transformation tangible.

Concepts became easier to evaluate when they could be seen, clicked, challenged, and discussed as possible product or service experiences.

← Back

Back to selected works.

This page keeps the project intentionally compact: enough to show facilitation, systems thinking, service design, and product strategy without over-exposing internal or client-specific details.

Go to works →