Most website advice assumes the visitor has a short attention span and needs everything simplified. That advice is wrong for a research organisation, where the audience is other researchers, clinicians and funders, and oversimplifying the work is the fastest way to lose their confidence.
Penn Clinical works on multimodal modelling of systems-level structure in complex disease. This is about building a site for a technical audience that needs the detail, without making it unusable for the funders and partners who need the summary.
Key Takeaways
- A research site’s credibility comes from methodological detail, not from simplified messaging.
- Two audiences need two depths: a readable summary layer for funders and partners, and full methodological scope for peers.
- Cohort and data engineering documentation belongs on the site, because it is how peers judge whether the work is sound.
- Clinical impact should be framed as what the work informs, not as outcomes it delivered.
What Does Penn Clinical Work On?
The organisation models multimodal, systems-level structure in complex disease. Its site sets out data and cohort engineering, core analytical capabilities, research programmes and methodological scope, alongside clinical impact areas including treatment selection criteria, tools aimed at preventing overtreatment, early dysmotility detection, cognitive fatigue typing, microbiome-guided therapy and anxiety-linked IBS.
That is a technical body of work, and the site does not pretend otherwise.
Why Should a Research Site Resist Simplification?
Because its most valuable readers are disqualified by it.
A researcher evaluating whether to collaborate, a clinician deciding whether a finding applies to their patients, and a funder assessing rigour all need to see the method. If the site reduces the work to accessible summaries, none of them can make their assessment, and the absence of detail reads as an absence of substance.
This is the opposite of the usual guidance, and it is worth being precise about why. Simplification helps when the visitor lacks context and the decision is simple. Here the visitor has more domain context than the person writing the website, and the decision is whether the science holds. In that situation, detail is the product.
Layer the depth rather than choosing one level
The resolution is not to pick an audience but to structure by depth:
- A plain-language layer at the top of each area, stating what the programme investigates and why it matters. This serves funders, journalists and clinicians outside the specialty.
- A methodological layer underneath, covering cohorts, data engineering and analytical approach. This serves peers, and it is where the credibility is established.
Both belong on the page, in that order. A visitor who needs the second reads past the first in seconds; a visitor who only needs the first is not blocked by the second existing below it.
Why Does Cohort and Data Engineering Deserve Its Own Section?
Because it is what a knowledgeable reader checks first.
In work of this kind, the finding is only as good as the cohort it came from and the pipeline that produced it. A peer assessing a claim about disease structure wants to know how the cohorts were assembled, what was harmonised, and what the data actually supports. Publishing that is not supplementary material, it is the argument.
It also does something useful for collaboration. Another group with a compatible cohort can see the fit before making contact, which is how research partnerships usually start.
How Should Clinical Impact Be Described?
Carefully, and this is the part where a marketing instinct does the most damage.
There is a real difference between “this work informs treatment selection criteria” and “this work improves patient outcomes”. The first is a description of what the research addresses. The second is a clinical claim, and a clinical claim needs evidence of a kind that a website is not the place to assert.
We hold to a simple rule on sites like this: the website describes what the work investigates and what it could inform. It does not claim clinical benefit on the organisation’s behalf. Overstating here is not a marketing risk, it is a credibility and potentially a regulatory one, and the audience most likely to notice is the one the site most needs to impress.
Framing impact areas as topics, which is what treatment selection, overtreatment prevention and early detection are, keeps the site accurate while still communicating relevance.
What Else Does a Research Site Need?
Programmes as durable structure
Research programmes change more slowly than findings. Organising the site around programmes gives it a stable spine, with outputs attaching to the relevant programme as they appear. A site organised around latest findings needs restructuring every time the emphasis shifts.
Background that establishes standing
The background section answers who is doing this work and in what context. For an unfamiliar visitor assessing an organisation they have not heard of, this is often the first page read and the one that decides whether they read a second.
Stated methodological scope
Saying what the group does and does not do is more useful than it appears. It prevents mismatched approaches, and a clearly bounded scope reads as confidence rather than limitation.
What We Would Watch
Research sites go stale in a particular way. Programmes finish, people move, and findings supersede earlier ones, but the pages describing them stay. A site listing a programme that ended two years ago as current is a credibility problem for exactly the audience that would notice. Each programme page needs a status and a review date.
The second is publication linking. Peers want the papers, and a site that describes work without linking to the published output asks them to go and search for it. Most will not.
Frequently Asked Questions
Should a scientific website simplify its language?
Not at the expense of the detail peers need. Layer it: a plain-language summary at the top of each section, full methodological detail below. Removing the detail removes the credibility.
What do funders look for on a research organisation’s site?
Evidence of rigour and of continuity: how cohorts were built, how analysis was done, which programmes are active, and who is responsible for them.
How should research be described without overclaiming clinical benefit?
Describe what the work investigates and what it could inform. Claims that a finding improves patient outcomes require clinical evidence and belong in publications, not on a website.
Should a research site have a blog?
Programme updates and published outputs serve better than a general blog. Frequency matters far less than whether the record of active work is current.
Communicating Technical Work?
If your organisation’s website simplifies the work to the point where a peer cannot evaluate it, the site is failing the audience that matters most.
See more of our builds in our portfolio, read how we scope projects on our process page, or get in touch.
