SERVICES

Engagement models to structure strategy and execution

Consulting and mentoring for organizations and leaders who need to turn complexity into operational clarity. Each engagement defines scope, cadence, metrics, and minimum deliverables.

Guilherme Atsumi in action

What consistently shows up in practice

Anonymous excerpts (survey). Focus on execution, clarity, and structure.

“Turns ideas into reality and structures the path to make it happen.”

“Sees the solution in stages and guides the conversation to the goal.”

“Builds bridges across people and areas — untangles knots and creates trust.”

“No fluff — when something needs to happen, he goes and makes it happen.”

“Connects people, ideas, and groups. Removes obstacles and enables collaboration.”

Engagement models

Don’t choose by “topic”. Choose by need and stage. The engagement model defines depth, timeline, governance, and implementation level.

Strategic sprint (diagnosis → direction → executable plan)

For when there is effort, but not enough clarity: priorities, decisions, scope, and cadence. Recommended for cycle starts, restructurings, accelerated growth, or high cross-functional noise.

When to use

  • Strategy disconnected from execution (many initiatives, limited outcomes)
  • Slow or politicized decision-making; informal dependencies
  • Fragmented portfolio (Product, Ops, CS, Engineering pulling in different directions)
  • Need clear direction within 2–6 weeks

What happens

  • Context diagnosis: pain points, constraints, stakeholders, risks
  • Decision criteria and scoping (what’s in / what’s out)
  • Objectives and expected outcomes (OKRs/KPIs, when relevant)
  • Initiative map with prioritization and explicit trade-offs
  • Execution cadence and minimum governance (forums, responsibilities, rituals)

Minimum deliverables

  • Synthesized diagnosis (hypotheses + evidence)
  • Direction and criteria (principles, trade-offs, decisions)
  • Tactical plan (initiatives, milestones, metrics, cadence)
  • Light governance model (RACI, forums, rituals)

Format: 2–6 weeks (intensive).

Structured project (design + assisted implementation)

To build durable processes, governance, and an operating model. Recommended when the organization needs to move from improvisation to sustainable execution.

Typical scopes

  • Process architecture and handoffs across areas (AS IS → TO BE)
  • Operating model and interfaces (Product, Engineering, CS, Operations)
  • Execution governance: rituals, responsibilities, decision forums
  • Metrics and dashboards (evidence-based management)
  • Critical journeys (onboarding, activation, adoption, support, retention)

How it’s run

  • Diagnosis and mapping (processes, decisions, artifacts, bottlenecks)
  • Target-state design (TO BE) with explicit criteria
  • Implementation plan (sequence, risks, dependencies, ownership)
  • Ritualization and minimum documentation for adoption
  • Evidence-based reviews (adjust based on system signals)

Deliverables and formats

  • Operating model blueprint (roles, rituals, forums, interfaces)
  • Process and decision maps (criteria + control points)
  • RACI and responsibilities
  • KPIs/OKRs + dashboards
  • Adoption kit (routines, templates, checklists)

Formats: fixed-scope project, or phased delivery.

Leadership (continuous governance and execution)

To sustain pace and quality over time, with governance and cross-functional integration. Recommended when there is a relevant portfolio, multiple dependencies, and a need for predictability.

Modalities

  • Program/Project Lead (end-to-end execution)
  • PMO (portfolio, cadence, risks, prioritization)
  • Operating model lead (interfaces across Product/Eng/CS/Ops)
  • Executive governance (forums, decisions, criteria, metrics)

What happens in practice

  • Scope, milestones, critical path, and capacity management
  • Risks, dependencies, and blockers (systematic handling)
  • Stakeholder communication (status, decisions, alignments)
  • Change management and impact control
  • Continuous improvement (lessons learned and evidence-based adjustments)

Expected outputs

  • More predictability (fewer surprises, stronger cadence)
  • Faster decisions (clear criteria and forums)
  • Less rework (designed interfaces, explicit handoffs)
  • Indicator-driven management (system signals, not opinions)

Format: monthly retainer, weekly/biweekly cadence.

Mentoring (execution, leadership, and transition)

Mentoring is structured in cycles: diagnosis, an applicable plan, and follow-up. The focus is criteria, decisions, and evidence-based execution — not endless conversation.

Startups and projects (impact and execution)

To structure operations, clarify demand, and build an execution plan with cadence and evidence. Experience with ecosystems and initiatives such as Gerando Falcões, ExpoFavela, and TETO.

  • Problem framing and decision criteria
  • Actionable backlog (now / next / why)
  • Minimum governance (rituals and responsibilities)
  • Progress metrics (learning, impact, sustainability)

Formats: 1:1, groups, cohort-based programs.

Leaders and teams

To increase decision and execution capability in complex environments: autonomy, alignment, governance, and operational clarity.

  • Prioritization, delegation, and trade-offs
  • Management rituals and operating agreements
  • Cross-functional interfaces (less friction and rework)
  • Negotiation and conflict management (when applicable)

Formats: 1:1, functional leadership, workshops.

Career transition

Narrative, positioning, and execution plan for transitions (role, function, industry, country). Hypothesis-driven approach with testing and iteration.

  • Direction and constraints (available energy, trade-offs)
  • Positioning and storytelling
  • 4–8 week plan with goals and evidence
  • Follow-up and results-based adjustments

Format: fixed cycle + follow-up.

Content, training, and speaking (applied learning)

Content development and learning experiences: courses, workshops, asynchronous materials, and talks. For topics and details, see Teaching →

What I deliver

  • Learning journeys and curricula (application + evidence)
  • Asynchronous content (text, video, exercises, assessment)
  • Hands-on workshops (tools, dynamics, facilitation)
  • Talks (governance, execution, processes, product, education, impact)

When it makes sense

  • Upskill teams without unproductive “theoretical training”
  • Standardize criteria (decision-making, prioritization, governance)
  • Increase execution maturity with usable instruments
  • Create a shared language across areas

Format: on demand (organization, event, or program).

How it works

A simple structure to reduce noise and accelerate high-quality delivery.

  1. Diagnosis — context, objectives, constraints, stakeholders, and success signals.
  2. Design — flows, governance, metrics, and routines (explicit criteria).
  3. Implementation — ritualization, minimum documentation, and enablement.
  4. Evolution — evidence-based adjustments: metrics, feedback, continuous improvement.

Let’s structure your execution system

If there is effort but not enough clarity, governance, and predictability, the first conversation focuses on context, constraints, and the expected outcome.