What Actually Changed When Marita Stavrou Started Pushing for Better Communication
I've been sitting in on grant review panels and journal editorial meetings long enough to notice when someone actually shifts the ground under everybody's feet. Marita Stavrou's work didn't read like another academic paper collecting dust. It read like someone pointing at the wall and saying the paint was peeling. The practical effect was immediate and a little annoying for people who were comfortable with the old way of doing things. Her core argument was straightforward but easy to ignore if you weren't paying attention: the machinery for moving research from publication to actual practice was broken, and nobody in charge of the machinery seemed interested in greasing the gears. She looked at the gap between what gets published and what practitioners on the ground can actually use, then built frameworks for closing it instead of just writing about the gap being a problem. One thing most people miss about her approach is that she wasn't arguing for more publications. She was arguing for better connectivity between types of output. A systematic review sits in a database. A clinical guideline sits in another one. A patient-facing summary sits somewhere else entirely. Her framework treated these as parts of a single pipeline rather than separate deliverables. That reframe changed how several funding bodies structured their dissemination requirements within about two years of her work becoming widely cited.
I ran into a specific edge case last year that made me think about this. We were preparing a dissemination package for a multi-site study and the journal wanted a plain-language summary formatted in their template, the funder wanted one in theirs, and our institutional review board wanted yet another version. The content was identical. The formatting and word choices were slightly different across three documents. I spent roughly half a day reconciling them before realizing the issue wasn't the content. It was that we had never built the original writing process to produce a single source document that could branch into different formats. After that mess, I started structuring all my team's outputs around Stavrou's layered dissemination model, where the raw evidence stays in one place and the different audience versions are extracted from it rather than rewritten from scratch each time. It cut our preparation time from about four days down to roughly a afternoon for a standard study. The counter-intuitive part that beginners overlook is that this method doesn't scale linearly with team size. Adding more writers to a project using this approach actually slows things down initially because everyone has to agree on the source document before any branching happens. You need one person who will own the primary content and say no when other people want to diverge from the evidence base. I've seen projects stall for weeks because the "owner" role was shared by committee. There's also a real limitation here that nobody talks about much. The framework works well for clinical and health research where the pathways are relatively standardized. It breaks down in fields where the audience segmentation is messier or where the end users span disciplines that don't share the same conventions. Social science research, for example, often has stakeholders who operate with completely different literacy expectations and different definitions of what counts as actionable. Forcing that through a rigid dissemination pipeline produces documents that satisfy the format but lose whatever nuance made the original work useful.
When that happens, the workaround is simpler than people think. Keep the core evidence document clean and let audience-specific versions be written independently by people who actually understand those audiences, rather than trying to force everything through a single template. It's less elegant on paper but it produces output that people actually read instead of filing away. The other thing her work exposed that most people took years to acknowledge: pre-registration and open data requirements alone don't solve the communication problem. You can have every dataset publicly available and still have zero practical impact if nobody in the chain between publication and application knows how to interpret what they're looking at. Stavrou's influence became visible in the field when funding bodies started requiring communication plans as seriously as they required data management plans. That shift didn't happen overnight but it happened faster than anyone predicted once her framework gave people a vocabulary for what they were actually missing. If you're trying to apply this to your own work, start by mapping who actually needs to use your research before you write a single word of the final output. Not who you think might. Who. Then write the source document for that specific set of users and branch from there. The temptation to write for everyone at once is strong. It produces nothing useful for anyone.
Get the Full Details
