---
title: "Pedagogy & Communication & Collaboration - José DA COSTA"
description: "Communication and collaboration, in my own definition, cover **4 distinct registers** I alternate every day. **Synchronous**: 1:1s, bi-weekly COPIL, incident war rooms. **Asynchronous**: RFCs, version"
locale: "en"
canonical: "https://portfolio.josedacosta.net/en/skills/pedagogy-communication-collaboration"
source: "https://portfolio.josedacosta.net/en/skills/pedagogy-communication-collaboration.md"
html_source: "https://portfolio.josedacosta.net/en/skills/pedagogy-communication-collaboration"
author: "José DA COSTA"
type: "skill"
slug: "communication-collaboration"
generated_at: "2026-06-02T15:37:55.860Z"
---

# Pedagogy & Communication & Collaboration

Icon: 💬

## My definition

Communication and collaboration, in my own definition, cover **4 distinct registers** I alternate every day. **Synchronous**: 1:1s, bi-weekly COPIL, incident war rooms. **Asynchronous**: RFCs, versioned ADRs, Confluence documentation, written memos right after the meeting. **Customer-facing**: advisory, contract negotiation, structured restitution of technical trade-offs in business language. **International**: operational English (**TOEIC 950**), mixed teams of internal staff plus contractors from three different companies. The thread from **MC Vendeur Multimedia** (in-store customer advisory) to **CTO Founder** (board-level conversation) is the same: meet the audience where they are, and write down the decision so it survives the meeting.

### Context

I rely on **3 structuring rituals**. **Weekly COPIL/board update**: a simple dashboard (progress, budget, risks, milestones) readable in under 5 minutes. **Daily team sync**: short standup, with an asynchronous Confluence channel for context. **Customer-facing commercial contact**: user interviews before each major evolution, paper prototypes validated before code. Editorial output: 19 portfolio references across these registers (DAM 1,400 users, ESB 80 daily interlocutors, PSR multi-partner API spec cycle).

### Relevance

In 2026, the **communication load** has been redistributed by distributed teams, AI-augmented work, and multi-vendor SaaS ecosystems. Collaboration tools now embed **AI agents that summarise threads, surface past decision context, and orchestrate next steps across time zones** without requiring a live meeting, a pattern Atlassian describes in [AI takes a seat on the team](https://www.atlassian.com/blog/teamwork/ai-insights-january-2026). The manager who cannot write for humans and agents at the same time loses half of their team's bandwidth.

## My evidence

### War room on a major Pichet ESB incident

**Context:** One peak day, a cascade of failures hit the ESB integration flows - payments, real-estate syndication, CRM updates - all at once. The **5 business directions** depended on those flows, and the incident threatened to block accounting entries, sales leads, and partner-portal listings simultaneously. On the communication side, I needed the business to understand what was going on without dragging the engineers into political back-and-forth.

**Action:** I opened a **synchronous virtual war room** with **2 distinct channels**: a technical channel for the on-call team, and a business channel for the department heads. I broadcast **hourly executive summaries** to the COPIL and the impacted directions, in plain language, no jargon - just the state of each flow, the estimated time to recovery, and what each direction had to do in the meantime. As soon as the situation stabilised, I ran a **blameless post-mortem** with the team and our Square IT and RS2I partners, with a written report published on Confluence within 24 hours.

**Result:** The **root cause** was identified and fixed in **3 hours**, and the post-mortem framework I shipped that day was adopted as the department standard for every subsequent critical incident.

**Value added:** Over the following 12 months, the **MTTR on the ESB platform was halved**, and the trust the 5 business directions placed in the integration team was durably rebuilt - they came back to me to scope 3 follow-up cross-functional initiatives that would never have shipped without that relational capital.

### Coordinating the DAM rollout to 1,400 users

**Context:** The November 2020 DAM Bynder go-live meant orchestrating in parallel the Communications Direction, Marketing, IT, legal, the vendors (Bynder, Activo Consulting, CI HUB), and **the 1,400 future users** spread across 8 Groupe Pichet entities (development, leasing, hospitality, student housing, marketing, communication, IT, executive office). Each spoke a different language: legal was thinking in contract clauses, business in daily usage, IT in infrastructure and SSO.

**Action:** I ran **17 weekly onboarding sessions** with the Bynder vendor across summer 2020 to carry the Pichet requirement to the editor without exposing the business to those calls. In parallel, I built a **transparent monthly reporting** to the COPIL with one simple dashboard: progress, budget, risks, milestones. For change management, I produced **persona-tailored training materials** (sales teams, communications teams, external partner agencies), because no 2 audiences consume a platform the same way. With Louise R. on the legal side, I led the full markup of the 3 Bynder contractual documents to lock SLA and reversibility down.

**Result:** **Go-live on the planned date**, **strong adoption** within the first weeks, **zero legal escalation**, and the executive satisfaction (Benoit P. as CEO, Remi E. as Director) explicitly formalised post-launch.

**Value added:** The trust capital built on this project later let me run **3 additional cross-functional initiatives** within the group without going through another evangelisation phase. The lesson: on a 1,400-user rollout, the quality of written communication and the regularity of reporting matter more than the technical brilliance of the deliverable.

### Holding the single point of contact role on the PSR platform

**Context:** For 3 years I steered the Pichet **PSR platform** (partner leads ingestion) at the intersection of marketing, IT and **a dozen external partners** (SeLoger, Myopla, Cooper Advertising, Akrivia Leads, Visibilitie, Clovis, Fine Media, Votre Appartement Neuf...). Each partner had its own format, its own protocol, its own people - and every lost lead represented potentially tens of thousands of euros in missed real-estate revenue. Internally I had to coordinate Franck C. (my manager), Cyril M. (Marketing IT), Emilie D. (external contractor), and the CRM operations team.

**Action:** I positioned myself as the **single technical point of contact** for every partner integration. I documented the **API across 5 consecutive versions**, wrote a **complete partner integration playbook** on Confluence, and personally trained each external partner team on the specs, authentication, and test procedures. For every new integration I ran a short cycle - spec, tests, business validation, go-live - with a clear responsibility matrix between the partner team, Marketing IT, and the CRM cell.

**Result:** **Partner onboarding lead time dropped from several weeks to a few days**, **zero major lead-loss incident** across 3 years, and the 2023 security audit passed without any major non-conformity despite the proliferation of APIM credentials.

**Value added:** That **single-point-of-responsibility** posture has become my default operating mode at ACCENSEO: on every customer engagement I am the single technical point of contact end-to-end, because that is what turns individual expertise into durable commercial trust.

## My self-critique

### Mastery level

Level **Senior**, with 4 registers practised every day (synchronous internal, asynchronous documentary, customer commercial, international English) and 2 operational languages. native French and operational English used for API specs and contract negotiation. Production credit: 19 portfolio references, including coordination of **1,400 users** (DAM Bynder) and animation of ~80 daily interlocutors (Pichet ESB). What still needs strengthening: **board pitch in English under heavy pressure** and TEDx-style public technical speaking.

### Importance in my profile

Force multiplier on every other pillar. The best architecture, strategy, or security decision has zero value if it is not transmitted - that is what turns individual expertise into team capacity (cf. [my posture on the about page](/en/about)) and makes contractual commitment possible (negotiated clauses, defended SLAs, audit responses).

### Advice (for myself and others)

My core hygiene rule: *always write the decision the moment the meeting ends*. Verbal alignment evaporates in 48 hours, the written record stays.

<u>To others:</u> prefer a short memo to a long deck, structure every written piece around the three questions *for whom, why, what do I expect back*. Treat asynchronous communication as an engineering discipline, review, proofreading, defined vocabulary.

## My evolution in this skill

### Role in my professional project

Communication is what makes my CTO scale-up role viable. Without it, I cannot align board, teams, customers and partners. In the 24-month plan, it lets me run a complete **board to team to customer** cycle staying legible across all 3 layers, and defend a tech budget or roadmap in front of an English-speaking investor board.

### Mid-term target level

By end of 2027, the observable goal is twofold: **pitch a tech strategy in 5 minutes** in front of an international board without a deck, and **chair a panel or keynote in front of 200+ peers**. The Senior-to-Senior+ shift is measured on these two deliverables - public English speaking is the main effort axis.

### Current training

Weekly English conversation with 2 international partners (UK and US), monthly executive coaching focused on public speaking, daily editorial OSS production (commits and READMEs in English on GitHub). Master in Software Engineering active until 2026, requiring most written production in proper French.

### Future training

TED-style public speaking program ([Toastmasters](https://www.toastmasters.org/) intensive or equivalent) planned 2026, executive storytelling workshop (Duarte / Stanford GSB) targeted 2027. Possible advanced business English program if the target role is English by default.

## Progression across journey

This skill was developed across 20 different journey items.

- **1997** - [BEP ICEF (Home Equipment Installer & Advisor), Specialization: Audiovisual Electronics & Antennas](https://portfolio.josedacosta.net/en/journey/bep-icef.md) (education) - Confidence: 1/5
- **1999** - [CTO · Founder · technical director](https://portfolio.josedacosta.net/en/journey/celiane-founder.md) (entrepreneurship) - Confidence: 2/5
- **1999** - [Vocational Baccalaureate in Household & Institutional Equipment Maintenance (MAEMC), Specialization: Electrical Engineering](https://portfolio.josedacosta.net/en/journey/bac-pro-maemc.md) (education) - Confidence: 1/5
- **2001** - [BTS IG (IT Management)](https://portfolio.josedacosta.net/en/journey/bts-computer-science.md) (education) - Confidence: 2/5
- **2001** - [Supplementary Certificate in Specialized Multimedia Product Sales](https://portfolio.josedacosta.net/en/journey/mc-vendeur-produits-multimedia.md) (education) - Confidence: 2/5
- **2008** - [Junior Software Engineer · PHP Joomla Webmaster Developer](https://portfolio.josedacosta.net/en/journey/ministere-sante-webmaster.md) (experience) - Confidence: 2/5
- **2009** - [Software Engineer · PHP Zend Framework Developer](https://portfolio.josedacosta.net/en/journey/european-sourcing-engineer.md) (experience) - Confidence: 3/5
- **2013** - [Senior Software Engineer · Lead PHP Symfony Developer](https://portfolio.josedacosta.net/en/journey/medialeads-senior-engineer.md) (experience) - Confidence: 3/5
- **2017** - [Senior Software Engineer · Lead PHP Magento Developer](https://portfolio.josedacosta.net/en/journey/smile-senior-engineer.md) (experience) - Confidence: 3/5
- **2019** - [Engineering Manager · Project Manager / Product Owner · Technical Lead](https://portfolio.josedacosta.net/en/journey/pichet-group.md) (experience) - Confidence: 4/5
- **2019** - [Technical Lead · Flows and Products: content and enterprise integration](https://portfolio.josedacosta.net/en/journey/pichet-technical-lead.md) (experience) - Confidence: 4/5
- **2020** - [Entrepreneur · Various Business Domains](https://portfolio.josedacosta.net/en/journey/auto-entrepreneur-jdc.md) (entrepreneurship) - Confidence: 4/5
- **2021** - [Project Manager / Product Owner · Flows and Products: PIM & DAM & ESB](https://portfolio.josedacosta.net/en/journey/pichet-project-manager.md) (experience) - Confidence: 4/5
- **2021** - [PSPO Certification (Professional Scrum Product Owner)](https://portfolio.josedacosta.net/en/journey/pspo-scrum.md) (certification) - Confidence: 4/5
- **2022** - [SAFe 5 Certification (Product Manager & Product Owner)](https://portfolio.josedacosta.net/en/journey/safe-po-pm.md) (certification) - Confidence: 4/5
- **2023** - [MBA Strategic Project Management](https://portfolio.josedacosta.net/en/journey/mba-strategic-project-management.md) (education) - Confidence: 4/5
- **2023** - [Master Expert in Software Engineering](https://portfolio.josedacosta.net/en/journey/master-software-engineering.md) (education) - Confidence: 4/5
- **2023** - [Engineering Manager · Enterprise Application Integration](https://portfolio.josedacosta.net/en/journey/pichet-engineering-manager.md) (experience) - Confidence: 4/5
- **2024** - [TOEIC Certification](https://portfolio.josedacosta.net/en/journey/toeic-950.md) (certification) - Confidence: 5/5
- **2024** - [CTO · Founder · technical director](https://portfolio.josedacosta.net/en/journey/accenseo-founder.md) (entrepreneurship) - Confidence: 5/5

## Related achievements

- [Trade Show Community Portal Platform](https://portfolio.josedacosta.net/en/achievements/portail-communautaire-salons-professionnels.md) - Collaborated with CEO, CTO, and Sales Director across European Sourcing ecosystem
- [EuropeanTool - B2B Promotional Product Platform](https://portfolio.josedacosta.net/en/achievements/europeantool-plateforme-b2b.md) - Coordinated with suppliers, resellers, marketing team, and external partners across 7 European countries
- [DAM Bynder - Project Manager for 1,400 Users](https://portfolio.josedacosta.net/en/achievements/dam-bynder-asset-management-project-manager.md) - Led 17 weekly onboarding sessions, user training, and transparent reporting to executive management
- [Partner Lead Reception API Platform (alias PSR)](https://portfolio.josedacosta.net/en/achievements/plateforme-api-reception-leads-partenaires.md) - End-to-end API integration lifecycle with external partners: specs, testing, validation, go-live
- [Akeneo PIM Project Management and Product Information Governance](https://portfolio.josedacosta.net/en/achievements/pilotage-pim-akeneo-migration-saas.md) - Managed knowledge transfer from predecessor, coordinated across development agencies, business teams, and vendor representatives
- [E-Commerce Platform Redesign Magento Enterprise Edition (alias Fleurance Nature)](https://portfolio.josedacosta.net/en/achievements/refonte-ecommerce-magento-fleurancenature.md) - Weekly progress meetings, iterative client reviews across 7 spec versions (30 to 50 pages), coordination with Smile PM, spec author, client PO and external providers
- [Engineering Manager - Enterprise Integration Platform (alias ESB)](https://portfolio.josedacosta.net/en/achievements/engineering-manager-integration-entreprise.md) - Translating between business languages (finance, hospitality, security), N+1/N+2 reporting, cross-team facilitation

Interactive version with navigation: https://portfolio.josedacosta.net/en/skills/pedagogy-communication-collaboration
