Packages and Process
summary
Case study of moving from manual reformatting to automated outputs at GSK: engineers build an R package that uses officer and flextable to write Word and PowerPoint, tags generated slides for QC, and integrates with existing pipelines rather than replacing them. A small team with a single-point decision maker scopes features, validates internally, and prioritizes fixes that cut turnaround time — reduced reporting time to under a week — while keeping nonprogrammers out of code.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:48Edsel failure lessons
- 4:28Slow process case study
- 6:14Workflow improvement
- 7:17New workflow expectations
- 8:23Team structure decisions
- 9:48Agile scope management
- 10:31Project success validation
- 11:40Edsel to GT design
- 14:45Conclusion and key takeaways
related talks
20mModernizing the Data Science Toolkit of a 40-year-old Market Research Company
28mEmpowering Teams: Transforming Your...
20mInstant Impact: Developing {docorator} to Simplify R Adoption for Teams
17mOddly Satisfying - Find delight in the mundane
40mThe Rocky Road to DocOps
16mSmall Package, Broad Impact: How I Discovered the Ultimate New Hire Hack
40mScaling testing & test automation without losing control
28mEffortless execution: Designing processes that don’t need babysitting
