Capability template for design and user experience
Current experience baseline
Before a redesign, the design lead gets a baseline built from the captures and page list they supply: each page read with its content and design observations, the patterns that recur, and the pages outside the evidence. The lead confirms the baseline and sets the scope.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
A redesign starts from a written record of what the site is today, not from memory. The design lead holds one inventory of the pages that were captured, what each says and shows, which patterns recur across them and where those patterns differ. Pages that could not be read, such as ones behind a sign-in, ones that change for each visitor or ones nobody captured, are named as outside the evidence so no one assumes they were covered.
The lead confirms the baseline, corrects it and decides the scope of the redesign. The capability records; it does not judge.
Who starts the work, and when
The design lead starts it when a redesign is being scoped and the current site needs to be written down first. People who capture pages, such as a designer or a content owner, prepare the inputs. The same baseline can be rerun on a later set of captures to see what has changed since the first.
What they supply
- A page list as a table: one row per page, with its address, name, section, the capture file, the capture date, how it was captured and an access note.
- The captures: screenshots, saved page text or saved page source, taken by a person with their own access. Nothing is fetched for them.
- Settings: the site's name, why the redesign is happening in one sentence, the page limit, and any names the team already uses for its patterns.
The capability opens no website, takes no capture and never asks for a password, a login code or a key.
What comes out
One baseline in a fixed order: what was supplied, coverage by section, a record for each page read, the patterns that recur and where they vary, the elements seen once, the places where pages say different things, the pages outside the evidence with the reason for each, names visible in the navigation that have no row in the page list, questions for the lead, and a confirmation block for the lead to fill in.
Where a section has nothing in it, it says so in words rather than being left out.
An invented example
Illustrative example with invented data. Marlowe Example Store is an invented online outdoor-gear shop, and Dana is an invented design lead; no real business or person is described. The pages, addresses, captures and words below were written for this example, and the addresses do not exist. A designer captured seven pages on 12 and 13 October 2026 and listed nine. The design lead supplied everything below, and the assistant ran the baseline from these files alone.
The inputs
The request
Please prepare the current experience baseline for Marlowe Example Store.
Lead: Dana. Reason for the redesign: replace the storefront theme before
the spring launch. Page limit: 40. No pattern names yet. My note: the
checkout header is reduced on purpose. Page list and captures follow.
The page list
Page ID,Address,Page name,Section,Capture file,Capture date,Capture type,Access note
P01,/,Home,Home,home-top.png,2026-10-12,screenshot-top,
P02,/shop,Shop all,Shop,shop-full.png,2026-10-12,screenshot-full,
P03,/shop/trail-jacket,Trail jacket,Shop,product-jacket.png,2026-10-12,screenshot-full,
P04,/cart,Cart,Checkout,cart.png,2026-10-12,screenshot-full,
P05,/help,Help centre,Help,help-text.txt,2026-10-13,saved text,
P06,/about,About,Company,about-full.png,2026-10-13,screenshot-full,
P07,/account,Account,Account,account.png,2026-10-13,screenshot-full,Shows the signed-in customer's own orders
P08,/wholesale,Wholesale portal,Wholesale,,,,Login required
P09,/returns,Returns policy,Help,,,,
The captures (screenshots shown here as a plain description of what each shows)
home-top.png (top of the page only)
Header: logo text "Marlowe"; links Shop, Help, About; "Cart (0)".
Hero: headline "Gear that outlasts the season"; line "Free returns for
60 days"; filled dark green button "Shop all", sized to its label.
Three cards in a row, each with a photo above its title: "Jackets",
"Packs", "Boots". The capture ends partway down a banner reading
"New for autumn". Headings are in a serif face, body text in a
sans-serif face.
shop-full.png
Header as on the home page, with "Cart (0)". Heading "Shop all" in a
serif face. A left column of filters: Category, Size, Price. A grid of
12 product cards in 3 columns and 4 rows; each card has a photo, a
name, a price and an outlined green button "Add to cart". Footer: three
link columns, Shop (Jackets, Packs, Boots), Help (Help centre,
Contact us), Company (About, Careers, Press); a box reading "Get 10%
off your first order" with an email field and a button "Sign up"; the
line "© 2022 Marlowe".
product-jacket.png
Header as on the home page, with "Cart (0)". Breadcrumb "Shop /
Jackets / Trail jacket". A gallery of 4 photos. Name "Trail jacket" in
a serif face; price "$189"; a size selector with XS, S, M, L, XL; a
filled dark green button "Add to bag", sized to its label. Three tabs,
Details, Care and "Reviews (0)", with Details open. Footer: the same
three link columns; a box reading "Join our list for 10% off your first
order" with an email field and a button "Join"; the line "© 2022
Marlowe".
cart.png
Header reduced: logo text "Marlowe" and the words "Secure checkout";
no other links. Heading "Your cart". A table with one line: "Trail
jacket", size M, quantity 1, "$189". "Subtotal $189". A filled dark green
button "Checkout" that runs the full width of the content area. Footer
reduced to one line: "Help centre | Contact us". No newsletter box.
help-text.txt (saved text; no layout)
Marlowe / Shop / Help / About / Cart (0)
Help centre
Search help
Orders / Shipping / Returns / Sizing / Payments / Contact us
Under Returns: "Free returns for 30 days on unworn items."
Shop: Jackets, Packs, Boots. Help: Help centre, Contact us. Company:
About, Careers, Press.
Sign up for 10% off your first order / Sign up
© 2022 Marlowe
about-full.png
Header as on the home page, with "Cart (0)". Heading "About Marlowe" in
a serif face, then one paragraph and a photo of a workshop. Heading
"Our story" with two paragraphs. Heading "Our materials" with a
bulleted list of three items. Footer: the same three link columns; a
box reading "Get 10% off your first order" with a button "Sign up"; the
line "© 2022 Marlowe".
account.png was also supplied (its content is not described here).
The result
CURRENT EXPERIENCE BASELINE: Marlowe Example Store
Draft baseline, not confirmed. For Dana. Reason for the redesign, as supplied: replace the storefront theme before the spring launch. Captures dated 2026-10-12 to 2026-10-13.
1. WHAT WAS SUPPLIED
Pages listed: 9. Captures supplied: 7. Page limit: 40. Capture files named but not supplied: none. Files supplied but not in the list, set aside, with any analytics, search or usage report named as supplied and not read: none. The lead's notes, labelled as the lead's notes and not as observations: "the checkout header is reduced on purpose". Not measured: contrast, type sizes, load speed, accessibility compliance, how pages look on a phone.
2. COVERAGE BY SECTION
Home: 1 read, 0 outside the evidence.
Shop: 2 read, 0 outside the evidence.
Checkout: 1 read, 0 outside the evidence.
Help: 1 read, 1 outside the evidence.
Company: 1 read, 0 outside the evidence.
Account: 0 read, 1 outside the evidence.
Wholesale: 0 read, 1 outside the evidence.
Total: 6 read, 3 outside the evidence, of 9 listed. Sections with no evidence: Account, Wholesale.
3. PAGE RECORDS
P01 Home, /, section Home
Capture: home-top.png, screenshot-top, 2026-10-12. The top of the page only.
Purpose as shown: headline "Gear that outlasts the season"; main action "Shop all".
Content in order: header (logo, Shop, Help, About, "Cart (0)"); hero with a line and a button; three category cards "Jackets", "Packs", "Boots"; a banner reading "New for autumn", begun. Levels not recorded.
Content observations: "Free returns for 60 days". The banner is cut off by the capture.
Design observations: as seen, the headings are in a serif face and body text in a sans-serif face; one filled dark green button sized to its label; three cards in a row, photo above title.
Not in this capture: everything below the start of the banner, including the footer; hover states; phone layout.
P02 Shop all, /shop, section Shop
Capture: shop-full.png, screenshot-full, 2026-10-12.
Purpose as shown: headline "Shop all"; main action: no single main action; "Add to cart" on each of 12 cards.
Content in order: header (as P01, "Cart (0)"); heading "Shop all"; filters Category, Size, Price; 12 product cards; footer with link columns Shop, Help, Company; newsletter box; "© 2022 Marlowe". Levels not recorded.
Content observations: 12 cards each with the button "Add to cart". Newsletter box "Get 10% off your first order", button "Sign up". Footer line "© 2022 Marlowe".
Design observations: as seen, the heading is in a serif face; filters sit in a left column; the cards are in 3 columns and 4 rows; the card buttons are outlined green.
Not in this capture: hover states; phone layout.
P03 Trail jacket, /shop/trail-jacket, section Shop
Capture: product-jacket.png, screenshot-full, 2026-10-12.
Purpose as shown: headline "Trail jacket"; main action "Add to bag".
Content in order: header (as P01, "Cart (0)"); breadcrumb "Shop / Jackets / Trail jacket"; gallery of 4 photos; name and price; size selector XS, S, M, L, XL; button; tabs Details, Care, "Reviews (0)"; footer with link columns; newsletter box; "© 2022 Marlowe". Levels not recorded.
Content observations: price "$189". Reviews tab reads "Reviews (0)". Newsletter box "Join our list for 10% off your first order", button "Join". Footer line "© 2022 Marlowe".
Design observations: as seen, the name is in a serif face; one filled dark green button sized to its label; three tabs with Details open.
Not in this capture: hover states; phone layout; the content of the Care and Reviews tabs.
P04 Cart, /cart, section Checkout
Capture: cart.png, screenshot-full, 2026-10-12.
Purpose as shown: headline "Your cart"; main action "Checkout".
Content in order: reduced header (logo, "Secure checkout"); heading "Your cart"; a table with one line; "Subtotal $189"; button; one-line footer "Help centre | Contact us". Levels not recorded.
Content observations: one line "Trail jacket", size M, quantity 1, "$189". Subtotal "$189". No newsletter box.
Design observations: as seen, one filled dark green button that runs the full width of the content area; header and footer reduced.
Not in this capture: hover states; phone layout.
P05 Help centre, /help, section Help
Capture: help-text.txt, saved text, 2026-10-13.
Purpose as shown: headline "Help centre"; main action: none shown in the text.
Content in order: header words "Marlowe / Shop / Help / About / Cart (0)"; heading "Help centre"; "Search help"; topics Orders, Shipping, Returns, Sizing, Payments, Contact us; footer words; newsletter words; "© 2022 Marlowe". Levels not recorded.
Content observations: under Returns, "Free returns for 30 days on unworn items." Newsletter words "Sign up for 10% off your first order", "Sign up". Footer line "© 2022 Marlowe". 6 topics.
Design observations: not observable from saved text.
Not in this capture: layout, images, colors and type faces.
P06 About, /about, section Company
Capture: about-full.png, screenshot-full, 2026-10-13.
Purpose as shown: headline "About Marlowe"; main action: none shown.
Content in order: header (as P01, "Cart (0)"); heading "About Marlowe"; one paragraph; a workshop photo; "Our story" with two paragraphs; "Our materials" with a bulleted list of three items; footer with link columns; newsletter box; "© 2022 Marlowe". Levels not recorded.
Content observations: newsletter box "Get 10% off your first order", button "Sign up". Footer line "© 2022 Marlowe".
Design observations: as seen, the heading is in a serif face; one photo; a bulleted list of three items.
Not in this capture: hover states; phone layout.
4. PATTERNS THAT RECUR
Site header (named by assistant): seen on 6 of 6 read pages (P01, P02, P03, P04, P05, P06). Forms: full, with logo, Shop, Help, About and "Cart (0)", on P01, P02, P03, P06, and as words only on P05 (saved text); reduced, with logo and "Secure checkout" only, on P04. Differences seen: the reduced form shows "Marlowe" and "Secure checkout" and none of "Shop", "Help", "About" or "Cart (0)" (the lead's note says this is on purpose). Not visible in this capture: none.
Footer (named by assistant): seen on 5 of 6 read pages (P02, P03, P04, P05, P06). Forms: full, with link columns Shop, Help, Company, a newsletter box and "© 2022 Marlowe", on P02, P03, P06; the same link groups, newsletter words and year line as saved text, words only, on P05; one line, "Help centre | Contact us", on P04. Differences seen: the one-line form "Help centre | Contact us" has no link columns, no "Get 10% off your first order" box and no "© 2022 Marlowe" line. Not visible in this capture: P01.
Newsletter box (named by assistant): seen on 4 of 6 read pages (P02, P03, P05, P06). Forms: one box with an email field and a button on P02, P03; one box with a button and no email field shown on P06; words only on P05 (saved text). Differences seen: "Get 10% off your first order" with "Sign up" on P02 and P06, "Join our list for 10% off your first order" with "Join" on P03, "Sign up for 10% off your first order" with "Sign up" on P05; see section 6. Not visible in this capture: P01.
Primary action button (named by assistant): seen on 3 of 6 read pages (P01, P03, P04). Forms: filled dark green, sized to its label, "Shop all" on P01 and "Add to bag" on P03; filled dark green, full width, "Checkout" on P04. Differences seen: "Shop all" and "Add to bag" are sized to their label; "Checkout" runs the full width of the content area. Not visible in this capture: P05 (saved text). The outlined card buttons on P02 are listed in section 5.
5. SEEN ONCE
Banner "New for autumn" (begun), P01. Hero with a line and a button, P01. Three category cards, P01. Filter column, P02. Grid of 12 product cards with outlined "Add to cart" buttons, P02. Breadcrumb, P03. Photo gallery of 4, P03. Size selector, P03. Three tabs, P03. Cart line table with subtotal, P04. The words "Search help", P05. List of six help topics, P05. Workshop photo, P06. Bulleted list of three items, P06.
6. WHERE PAGES SAY DIFFERENT THINGS
Return period: "Free returns for 60 days" on P01; "Free returns for 30 days on unworn items." on P05.
Label for adding an item: "Add to cart" on P02; "Add to bag" on P03. The header link on both reads "Cart (0)".
Newsletter wording: "Get 10% off your first order" on P02, P06; "Join our list for 10% off your first order" on P03; "Sign up for 10% off your first order" on P05. Button: "Sign up" on P02, P05, P06; "Join" on P03.
7. OUTSIDE THE EVIDENCE
P07 Account: O3, the Access note says "Shows the signed-in customer's own orders"; account.png was supplied and not read. To bring it in: a person captures a view that carries no real customer's data, or the lead confirms it stays out.
P08 Wholesale portal: O1, no capture file; O3, the Access note says "Login required". To bring it in: a person with access captures it, or the lead confirms it stays out.
P09 Returns policy: O1, no capture file. To bring it in: a person captures it, or the lead confirms it stays out.
8. VISIBLE NAMES WITH NO ROW IN THE PAGE LIST
Jackets: seen on P01 (category card), P02, P03, P05, P06.
Packs: seen on P01 (category card), P02, P03, P05, P06.
Boots: seen on P01 (category card), P02, P03, P05, P06.
Contact us: seen on P02, P03, P04, P05, P06.
Careers: seen on P02, P03, P05, P06.
Press: seen on P02, P03, P05, P06.
9. QUESTIONS FOR THE LEAD
1. P07 Account has a capture but its access note says it shows a customer's own orders. Should it stay outside the evidence, or should a person capture a view with no real customer's data?
2. P01's capture ends partway down the page. Is a full-page capture needed to see its footer?
3. P05 was supplied as saved text. Should a screenshot be supplied to bring its design observations in?
4. Should the six names in section 8 be added to the page list, or stay outside the redesign?
5. P08 and P09 have no capture. Should they be captured, or stay out?
10. THE LEAD'S CONFIRMATION
Baseline: [to be completed by the design lead.]
Changes to make: [to be completed by the design lead.]
Scope of the redesign: [to be written by the design lead.]
Confirmed by and on: [name and date, to be completed by the design lead.]
Every record traces to the capture it names, dated as shown, for Marlowe Example Store. The baseline visits no site, takes no capture, designs nothing and ranks nothing, and it sends nothing.
What to check in this result
- Nine pages were listed: six read and three outside the evidence, and the section counts add up to the same totals.
- The read pages are P01 to P06. P01's capture ends before its footer, so the footer is counted on 5 of 6 read pages (P02, P03, P04, P05, P06) and P01 is listed as not visible.
- The newsletter box is on four read pages: P02, P03, P05 and P06.
- Nothing was rated. The two return periods are recorded side by side; which is right is for Dana and the content owner to settle.
Where it fits
- Design and user experience, where a redesign has to start from what exists.
- Product management, where scope depends on knowing what the current experience contains.
- Software and technology, where products and marketing sites grow page by page.
- Ecommerce and retail, where storefront, product and checkout pages are built at different times.
- Education, where a site spans admissions, programs and student services.
- Professional services, where a firm's site mixes practice pages, people pages and insights.
- Growth & scaling, when a site built for a smaller company has to carry a larger one.
- Established businesses, when a long-lived site has never been written down.
It records a site's pages and patterns from captures. It does not audit an old campaign's assets (inherited campaign audit), plan how files in a shared folder are organized (shared folder filing plan), or look inside a design library (component inventory audit). It proposes no design and ranks nothing.
What has to change for your company
- Your page list columns. Use the default headers or rename your export's columns once. When a header does not match, the assistant stops and asks.
- Your sections. Group pages the way your team talks about the site.
- Your page limit. Choose how many pages one baseline covers.
- Your pattern names. Supply the names your team already uses, or accept descriptive ones.
- Your access words. Say which words in the access note mean a page is restricted, personalized or not visited.
- Who confirms. Name the design lead and who else reads the baseline before the scope is set.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried once on its invented example in Claude on 10 November 2026, and the record is published with it. It has not yet been tested in a client environment, or as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a small section of a site the design lead already knows, with cases written in advance: a page behind a sign-in, a page that shows different content to different people, a capture that stops partway down, a page listed with no capture, and two pages that give different answers to the same question. The design lead checks every record against the capture it names before anyone relies on the baseline. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: