Collaborating w/teams on content strategy planning: pitfalls & best practices
summary
Argues that success hinges on specifics: establish clear communications up front, schedule regular touchpoints, and decompose work into visible chunks with deadlines; budget actual people time and QA slots instead of just tool licenses; use project tools like Jira/Asana/Trello and Slack channels to keep work traceable; run a pilot/proof of concept and set up a test environment (example: choose a localization management system and have a test instance within six weeks) so dependencies reveal themselves and fixes get made before full rollout.
AI-written summary · about
chapters (9)
- 0:00Introduction and scope
- 1:36Establishing communication
- 3:27Common planning pitfalls
- 6:02Impact, budget and resources
- 8:53Aligning with business goals
- 12:43Tactical implementation
- 16:15Quality assurance and testing
- 21:21Concluding remarks
- 21:52Q&A session
related talks
35mSuccessfully Integrate Teams of Internal and External Developers
45mContent Amid Chaos
19mPlatform Design & Content Strategy
01h 10mAgile Cross Team Collaboration How Tos
49mAll Aboard: Tools and Tactics for Building Team Consensus.
43mDesign Beyond Deliverables
39mThe Pains of Composition: How to write your best documentation in a collaborative world
19mCross-functional Relationships: Content Strategy for Designers