He retains his technical judgment while learning not to solve every problem himself.
Operations director · Characters
07 / 31OUR SERIES / CHARACTERS
Diego Serrano
He wants the team to make decisions; under pressure, his hand reaches for the keyboard first. A technical manager learning to share context and wait.
Continue reading
PROPOSED ACTING01
Character · profile and arc
With a background in computing, he trusts himself to solve problems quickly. He wants a capable, autonomous team; when pressure builds, he may take the mouse, make corrections, and finish someone else’s task. The dramatic conflict is in the gesture: promising autonomy, then stepping in before it can happen.
An ordinal editorial scale for writing fiction: it is not an evaluation, diagnosis, or measurement. Both ages and all values are proposals; the future profile is a hypothesis, not progress that has already happened. This profile does not record any confirmed progress.
- 01
Starting point · proposal
Solving it himself
When a blocker appears, Diego reaches for the keyboard first and leaves less room for someone else’s diagnosis.
CHARACTER READING - 02
Experiment · narrative hypothesis
Share context and listen
The change explored by the series is to wait, ask about priorities, and trust the team’s judgment.
PROPOSED ARC - 03
Pace · nonlinear
Progress with setbacks
Changes are small writing experiments, not an instant transformation. No episode-by-episode progress is confirmed here.
NO CONFIRMED PROGRESS
- Goal
A high-performing, autonomous team.
- Contradiction
Urgency pushes him to step in just when he has delegated.
- Narrative challenge
Share context, listen, and let the team find its own solution.
- I’ll do it myself
He solves problems quickly and takes tasks back when others are slow; he needs to learn to delegate.
- Perfectionism
Effort can turn into pressure and a need to prove his worth.
- Techie interests
He prefers systems and references not everyone understands; he can leave others out.
Enlarge infographic ↗Structural reference: “Character profiles…” · Javier Miró ↗. Structural reference consulted through an automatic transcript; Diego’s details and relationships are our own editorial adaptation.
02
Visual guide · views, poses, and ages
His visual identity centers on a blue shirt, his gaze fixed on the screen, and a hand reaching for someone else’s mouse just after he has promised to delegate. The following sheets are character-design proposals; they are not animation frames or approval.
Enlarge original ↗Enlarge original ↗
Enlarge original ↗
Enlarge original ↗03
Relationships · asymmetric ties
12 direct ties and 6 possible contextual encounters. The perspectives are editorial; these encounters imply neither regular contact nor events that have occurred.
Diego Serrano → Maribel SalcedoAppreciates: Diego may value Maribel spotting the error that would have turned his quick fix into another problem. May frustrate him: Diego finds it exasperating when Maribel turns a minor typo into a full review.
Maribel Salcedo → Diego SerranoAppreciates: Maribel may value Diego finding a technical cause and explaining how it affects the rest of the process. May frustrate her: Maribel is irritated when Diego takes the work away just as she expected him to recognize her effort.
Friction: As they finish an incident report, Diego tries to take the file away to correct it; Maribel insists that one figure still needs to be explained.
Possible development: Diego hands the file back and agrees with Maribel on which error needs correcting. She limits the review to that criterion and agrees to close out the rest.
Diego Serrano → Nicolás “Nico” LinAppreciates: Diego values Nico identifying a technical cause that was not visible on the tracking dashboard. May frustrate him: Diego worries that he cannot tell whether Nico is making progress because Nico investigates in silence.
Nicolás “Nico” Lin → Diego SerranoAppreciates: Nico may recognize Diego’s ability to connect the failure to its operational impact and prioritize it. May frustrate him: Nico dislikes it when Diego takes the keyboard and turns a question into an intervention.
Friction: An incident affects the portal, and Diego moves toward Nico’s keyboard before Nico has finished diagnosing it.
Possible development: Diego asks for the status and the next check before touching anything. Nico gives a brief update and provides a diagnosis they can both translate into a priority.
Diego Serrano → Francisco “Paco” AguirreAppreciates: Diego may value Paco remembering a real-world exception that is not in the procedure. May frustrate him: Diego is frustrated when Paco defends the old step without comparing its results.
Francisco “Paco” Aguirre → Diego SerranoAppreciates: Paco may value Diego connecting the proposal to a priority rather than just a technical preference. May frustrate him: Paco is irritated when Diego asks for speed without knowing why that check was added.
Friction: Diego proposes replacing a step in the incident protocol; Paco asks which specific failure the change would prevent.
Possible development: They review a real case together and agree to test the change only for that type of incident. Paco keeps the documented exception; Diego stops presenting speed as the only benefit.
Diego Serrano → Alejandro “Álex” DuarteAppreciates: Diego may recognize Álex’s ability to get a client to agree to an initial conversation. May frustrate him: Diego is irritated when Álex presents contacts as if they were closed sales.
Alejandro “Álex” Duarte → Diego SerranoAppreciates: Álex may value Diego turning a promising conversation into clear steps and criteria. May frustrate him: Álex dislikes Diego measuring the account with a table that fails to reflect the work involved in opening the door.
Friction: During an account review, Álex uses an entry from Rafael’s calendar as evidence of performance, and Diego asks about the follow-up result.
Possible development: Álex records who facilitated the contact and takes responsibility for the follow-up; Diego recognizes that Álex opened the door and evaluates the outcome without giving him credit for someone else’s contribution.
Diego Serrano → Sonia CárdenasAppreciates: Diego may value Sonia spotting dependencies before a delivery gets stuck. May frustrate him: Diego is unsettled when Sonia brings up her accumulated workload only after she is already angry.
Sonia Cárdenas → Diego SerranoAppreciates: Sonia may value Diego’s ability to reassign priorities when the workload becomes unreasonable. May frustrate her: Sonia is irritated when Diego treats her reliability as a reason to give her another task.
Friction: Diego gives Sonia an urgent task because he trusts her to handle it; Sonia shows him the tasks that have already piled up on her board.
Possible development: Sonia lays out her workload before accepting another urgent task. Diego removes a task or assigns a different owner, and they both stop treating “she always handles it” as a plan.
Diego Serrano → Julián FerrerAppreciates: Diego may value Julián bringing an unspoken disagreement to light when the team would not raise it in front of the boss. May frustrate him: Diego dislikes a team-climate meeting ending without an owner or next step.
Julián Ferrer → Diego SerranoAppreciates: Julián may value Diego turning what he hears into a verifiable operational decision. May frustrate him: Julián is frustrated when Diego treats the team’s discomfort as a delay to skip.
Friction: After a complaint in a meeting, Diego asks for an action, and Julián suggests a brief conversation to find out whether others share the problem.
Possible development: First they agree on whether they need to hear from more people, then on who will decide. Julián keeps the session focused on that question; Diego incorporates what they learn into the decision.
Diego Serrano → Lucía RoldánAppreciates: Diego values Lucía knowing who is arriving and preventing a visitor from getting lost in the office. May frustrate him: Diego worries that Lucía confirms before checking and leaves the team no room to adjust.
Lucía Roldán → Diego SerranoAppreciates: Lucía values Diego clarifying who will meet the visitor and correcting the procedure. May frustrate her: Lucía is embarrassed when Diego corrects her mistake in front of the visitor.
Friction: An important visitor arrives, and Lucía directs them to a room whose availability she has not checked; Diego asks to change the route.
Possible development: They create a quick check for room and host. Lucía verifies before making a promise, and Diego corrects her privately when the situation allows.
Diego Serrano → Bruno MeyerAppreciates: Diego may recognize Bruno’s knowledge of service incidents and the procedures that contain them. May frustrate him: Diego is irritated when Bruno changes his tone in front of him and mistakes the absence of complaints for a healthy team climate.
Bruno Meyer → Diego SerranoAppreciates: Bruno may value Diego taking responsibility for a decision that affects the team instead of delegating the disciplinary boundary. May frustrate him: Bruno dislikes Diego questioning his methods without seeing the pressure of operations.
Friction: Bruno waits for Diego to leave before reprimanding an operator; when Diego returns, he finds a team that has stopped reporting problems.
Possible development: Diego listens to the people affected and sets an explicit limit on shouting. Bruno explains the incident with data and accepts that experience does not give him license to intimidate people.
Diego Serrano → Tomás SalinasAppreciates: Diego may value Tomás’s specialist knowledge when Tomás connects it to the decision at hand. May frustrate him: Diego dislikes not knowing whether Tomás is addressing the question or avoiding it.
Tomás Salinas → Diego SerranoAppreciates: Tomás may value Diego clarifying why he needs the consultation and which decision depends on it. May frustrate him: Tomás is uncomfortable when Diego turns a consultation into an interrogation about availability.
Friction: During a remote consultation, Diego asks who confirmed a figure; Tomás looks off-camera and blames the silence on the connection.
Possible development: They agree that Tomás will confirm the figure or state the limits of his answer, and that Diego will assign any remaining verification. The camera is no longer a substitute for a clear answer.
Diego Serrano → ElenaAppreciates: Diego may value Elena noticing the human cost of his plan before the day turns into another checklist. May frustrate him: Diego feels Elena is slowing the plan down when she questions an improvement he believes is useful.
Elena → Diego SerranoAppreciates: Elena may value Diego turning a family intention into a concrete plan when he also listens to her needs. May frustrate her: Elena resents Diego’s system leaving her to carry out the tasks he designed.
Friction: They plan a family outing and Diego designs an efficient itinerary; at dawn, nobody has taken responsibility for making breakfast.
Possible development: They split breakfast, packing, and the route between them and leave one part of the day unscheduled. Diego helps with the preparations; Elena is not the default person in charge.
Diego Serrano → Carmen OrtegaAppreciates: Diego may value Carmen asking what a solution costs over the whole year. May frustrate him: he is irritated when she argues over small expenses but does not question the hour he spent automating the task.
Carmen Ortega → Diego SerranoAppreciates: Carmen may value Diego spotting a recurring cost no one else had noticed. May frustrate her: she is irritated when he spends three hours saving thirty seconds, then calls the cost of a useful tool excessive.
Friction: An automation promises future savings, but it comes with a subscription and maintenance. Carmen gets stuck on the monthly charge; Diego falls for the theoretical savings.
Possible development: They agree to a limited trial that records cost and time before renewal, though Diego may expand the system again and Carmen may argue over the charge without checking usage.
Diego Serrano → Damián VelaAppreciates: Diego may value Damián reconstructing a mapping between sources that no one had documented properly. May frustrate him: he is irritated when Damián leaves the ticket half-done to go to the gym.
Damián Vela → Diego SerranoAppreciates: Damián may value Diego spotting the business priority behind an integration failure. May frustrate him: he is irritated when Diego takes over the keyboard while he is still explaining the mapping, then asks for documentation he left no time to write.
Friction: The issue is urgent and Damián’s record is incomplete; Diego’s immediate intervention may fix it while reinforcing the dependency he later criticizes.
Possible development: Diego asks before taking over the keyboard, and Damián leaves a brief note before leaving, with setbacks when time is tight.
Enlarge original ↗