Packages and Process
summary
GSK builds an R-based pipeline that converts programmer outputs into publishable Word/PowerPoint with officeverse and flextable, cutting end-to-end reporting from weeks to under a week. A small cross-functional team, one decision owner, and strict scope prevent feature bloat; existing Office formats are reused, automated QC tags flag generated content, non-programmers need no code, and the solution passes internal validation so downstream writers stop reformatting and re-QC.
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
17mBreaking Barriers: Adopting R in Biotech with Posit
19mApproaches to Assay Processing Package Validation
16mShip Production Software in Minutes, Not Months
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
27mProduction pipeline without clogging
59mReplatform in a Year or Die: The Tale of a Turnaround
27mCrossing the transformation finish line