Role Breakdown
Two ruled lists side by side naming what the author owned versus what named teammates contributed, with honest framing about the credit split.
Two ruled lists side by side naming what the author owned versus what named teammates contributed, with honest framing about the credit split.
Search blocks by description or jump to a page.
The source for every Portfolio block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Role Breakdown names the credit split on a four-person cross-functional project: six items in the left column covering research, wireframes, visual design, copywriting, and QA, all owned solo, and four items in the right column naming each teammate by discipline and real name (Priya Nair, Marcus Kim, Jordan Lee, Daniel Ross) with their specific contributions. The framing sentence says the credit split matters before the lists begin.
The two columns are two separate arrays. Naming teammates by name and discipline rather than just listing their functions is the distinctive detail, it reads as acknowledgment rather than accounting.
Reach for this block in any case study where the work was collaborative and a reader could reasonably wonder what you specifically did. The installer updates both lists to reflect their real contribution and their actual teammates, keeping every name accurate.
A natural flow around it on a Portfolio Pro page:
Before
After
One strong use is the cross-functional UX project split. Other role breakdown shapes:
Tip: a case study with no teammate names reads as though the person worked alone on every project, which is rarely true and rarely more impressive than the truth.