This is a guest blog from Thomas Chan, a Ditto contributor and longtime leader in content design, localization, and content ops.

-----

In the world of digital products, content designers are well-positioned within the value stream. We have a bird’s-eye view of every workflow, what each stakeholder does, and where things may get stuck. This clarity gives content designers the disinterested view to make a fair judgment on whether the value stream setup is effective.

What can one do with this clarity? While this knowledge can enhance a content system, it’s also a golden opportunity to uplift the entire value stream by putting the insights to good use. In this article, I’ll showcase and explain why being in the centre of a workflow allows content designers to effectively lead improvements and retrospectives, how to lead them, and how to bring everyone on board.

Content’s position in a digital workflow

Before focusing on retrospectives, let’s review content designers' placement: we typically overlap with other functional teams and rely on their efficiency. This exposure lets us spot workflow issues and understand each party's goals and different product needs and timetables from an outsider perspective.

For example, when I worked in content design on a card product, my stakeholders included UX, product delivery, translation, developers, and graphic design. Sitting at the centre of the workflow let me see blockers, understand functional needs, and track ticket movement efficiently.

Kaizen: continuous improvement

Complementing this clarity is an essential Agile concept that drives continuous improvement. The Kaizen (Japanese for improvement) mentality helps project managers improve workflows through continuous iterations. Instead of making big or disruptive changes all the time, Kaizen emphasises incremental changes that fix one thing at a time, meaning we only strive to declutter our workflow whenever blockers arise without overhauling it.

When bringing kaizen into practice, content designers can observe other teams’ sprints, or empathise with them as we work alongside them. As a result, they can unveil where things get stuck and how communications can be more effective from a different angle.

Returning to the card product example, knowing creative lead times, unclear briefs, or slow sign-offs allows me to identify issues and empathise. For instance, if developers are constantly stalling because they lack edge-case copy, a quick Kaizen fix is baking error states right into the main design components or giving copywriters more clarity with the right documentation. Or, if engineering is getting buried under copy changes mid-sprint, you might introduce a simple forty-eight-hour copy freeze before handoff.

Some problems, like unclear form fields, are fixable; others may need broader discussion. What’s feasible depends on trust, communication, and established relationships.

Retrospective: the key to workflow optimisation

Retrospectives are Agile’s primary tool for continuous improvement. These regular meetings recognise hard work, highlight improvements, and identify action items. A successful retrospective fosters honest, constructive discussion without blame.

A typical retrospective has the following steps:

• Step 1: Make sure everyone feels comfortable sharing their thoughts. You can do this by adjusting the meeting environment or offering alternative ways for people to provide feedback, such as written or one-on-one channels.
• Step 2: Have your backlog ready — everyone should be able to add their insights and suggestions beforehand.
• Step 3: Start the retrospective by creating a welcoming, safe atmosphere. Encourage open participation, but let people opt out if they prefer.
• Step 4: Review feedback together. Discuss what went well, what needs improvement, and what blockers arose—focus on facts, not blame. For content designers, this is where you look at why copy handoffs felt rushed, or where design constraints and character limits clashed in Figma. 
• Step 5: Summarise the discussion with clear next steps. Store completed action items in a shared location for future reference. Keep these action items sharp and owned—like assigning someone to document component specs or setting up a clearer sign-off loop, and reporting back to the team periodically.  

In content design, retrospectives can also review project tone, project length, any UX/UI pitfalls, and blockers in cross-functional workflows. These three elements are key to a successful cross-functional retrospective.

Identifying and fixing issues

The goal of a retrospective is to find actionable solutions for existing pain points. Open discussion allows everyone to contribute. In cross-functional retrospectives, consider the challenges your team and others face objectively.

Then, fix what you see: Do we need new tools, better communication channels, templates, or other improvements? If you have immersed yourself in the workflows long enough, now is a good time to speak up. This might mean building an upfront briefing template to stop ad-hoc requests, or designing a shared checklist to get legal and compliance sign-offs earlier in the cycle. 

Communicate flexibly

There’s no single best approach to communication. While Agile prefers face-to-face, remote teams or those who prefer otherwise can run retrospectives via messaging or shared docs. What matters is tracking actionable and completed items.

Although your suggestions across functions are likely well-intentioned, resistance may arise when you contribute to others’ retrospectives. In these situations, stay objective and practical: demonstrate your insight into blockers and readiness, and offer potential solutions. Remain empathetic, persistent, and patient.

Psychological safety for all

There are four levels of psychological safety in group environments: inclusion safety, where members feel safe and valued; learner safety, where asking questions is without consequences; contributor safety, where comfortably participating and adding value is possible; and challenger safety, where suggesting improvements is possible.

For a functional retrospective, the host or content designer leader should at least strive for learner safety. This means everyone can speak up or participate. For better outcomes, strive for contributor safety. The only way to achieve this is through creating a no-blame, positive environment where everyone focuses on improving things. And if things did go well, don’t hesitate to compliment your colleagues.

By combining a central workflow role with a continuous improvement mindset, content designers play a pivotal role in strengthening cross-functional collaboration. Leading retrospectives and championing psychological safety, they are equipped to uncover inefficiencies, foster open communication, and drive meaningful change across digital product teams.