Selected operating evidence

A record of making fragmented work governable.

This page uses verified roles, public projects, and representative artifact structures instead of unsupported client metrics. Private client systems, credentials, pricing, and identifying details remain private.

Executive Director Canadian Chamber of Commerce in Japan
Since 2009 operating in Japan across institutional, commercial, cultural, and independent work
Strategy + delivery decision maps, roadmaps, implementations, runbooks, and operating handoffs

Operating record

The same method across different systems.

Professional network · Tokyo

Platform and operating responsibility

Role or projectWeb systems, content, member experience, and technical coordination
PeriodAdvisory work since 2023

Operating context

Digital work crossed websites, domains, content, member experience, technical dependencies, and operating decisions without one simple boundary between strategy and delivery.

Verified record

The verified role record covers digital strategy, platform priorities, updates, technical dependencies, and operating coordination across the network.

Responsibilities and work

  • Connected platform decisions to member and operating needs
  • Worked across technical, content, and organizational dependencies
  • Kept strategic recommendations close to practical delivery

Evidence shown here

  • System and platform recommendations
  • Website and content system improvements
  • Operating guidance and technical coordination

Business chamber · Tokyo

Verified institutional leadership

Role or projectBoard, committees, members, communications, events, and public resources
PeriodExecutive Director, 2019 to 2020

Operating context

A member organization required coordination across governance, committees, communications, events, partnerships, public information, and daily operating demands.

Verified record

Independent records establish Matt as Executive Director from 2019 to 2020, responsible for translating board and member priorities into institutional operations and public facing work.

Responsibilities and work

  • Coordinated board, committee, member, and stakeholder activity
  • Managed communications, events, partnerships, and public resources
  • Worked across leadership intent and day to day delivery

Evidence shown here

  • Member and stakeholder communications
  • Event and partnership operations
  • Public information and organizational resources

Independent cultural platform · Japan

Documented platform and event production

Role or projectEvent production, publishing, audience systems, and scene documentation
PeriodKaala and related cultural work

Operating context

Underground music activity was fragmented across venues, performers, promoters, archives, and audiences, with no single reliable operating or discovery layer.

Verified record

The public project record documents event production, publishing, archives, audience development, and practical discovery tools built around the underground music scene.

Responsibilities and work

  • Produced and documented events across independent music communities
  • Connected artists, venues, audiences, publishing, and promotion
  • Built systems and public resources around fragmented cultural information

Evidence shown here

  • Event and production operations
  • Publishing and audience infrastructure
  • Structured public history and discovery tools

Independent property intelligence venture · Japan

A separate property intelligence venture

Role or projectResearch, property information, publishing, and advisory workflows
PeriodAkiya and Inaka, separate from MKUltraman

Operating context

Rural property information was scattered across local listings, public records, municipal programs, and inconsistent source formats.

Verified record

The project record documents property research, local context, publishing, and inquiry workflows. It remains separate from MKUltraman and is not presented as licensed brokerage.

Responsibilities and work

  • Combined fragmented sources into structured property context
  • Built research and publishing workflows around public information
  • Kept advisory boundaries distinct from regulated brokerage claims

Evidence shown here

  • Structured property intelligence
  • Research and publishing workflows
  • Decision support with explicit role boundaries

Representative deliverables

What the work can leave behind.

Written artifacts belong to engagements that include written work. The $175 Technology Decision Session is a live conversation and includes no report, memo, or written follow-up.

Representative redacted Technology Health Check report showing findings, summary structure, and blocked client details.
Written diagnostic

Technology Health Check report

A written report that maps the relevant tools, ownership, dependencies, and material risks, then prioritizes what leadership should examine next.

Representative first page layout with identifying, financial, vendor, and internal operating details redacted.

  • Tool, workflow, and ownership map
  • Dependencies and material risk register
  • Prioritized findings for the debrief
Representative redacted roadmap showing phased work, owners, dependencies, and blocked client specific tasks.
Roadmap and execution plan

Infrastructure roadmap and implementation plan

A scoped working document showing the target state, sequence, dependencies, owner responsibilities, verification conditions, and implementation boundary.

Representative implementation structure with client specific systems, owners, and tasks removed.

  • Target state and scope boundary
  • Sequence, dependencies, and named ownership
  • Handoff and verification conditions
Representative redacted operating runbook showing admin notes, workflow rules, and maintenance sections with sensitive content blocked.
Runbook

Operating runbooks

Documentation the next owner can use after delivery: access responsibilities, workflow rules, reporting logic, escalation paths, and maintenance guidance.

Representative runbook structure with credentials, vendor names, and internal procedures redacted.

  • Admin and access responsibility map
  • Workflow, exception, and escalation notes
  • Reporting logic and maintenance checklist

Start here

Need this kind of clarity on a Japan-side system?

Start with the free Technology Risk Self-Check or request a 45-minute Technology Decision Session for $175. If the problem is structural, the next engagement may be a written Technology Health Check.

The 45-minute Technology Decision Session is $175 and includes focused live discussion and candid judgment. It does not include a report, memo, implementation plan, or written follow-up. Written diagnosis starts with the Technology Health Check from $1,000.