{Optional subhead to briefly intro how to solve the issue the page addresses}
{Page description from IA: [Solution topic] solutions include [types of products, services, etc.] to [enable][specific capabilities].}
{After the wiki-description, start a new paragraph that, first, describes the client challenge in one or two sentences, illuminating the primary pain point while identifying with the target audience's current mental model.
Then, hint at the new way of doing things that the solution offers. Highlight what makes the the IBM solution special compared to peers—be specific and consider this structure: This IBM [differentiated solution type] delivers [value] using [product feature] or [service capability]. Next, elaborate on additional differentiators and any technical ways the solution provides value and uniquely solves the client problem. Include IBM’s unique POV.
Break the copy into multiple paragraphs or subsections, if needed, to improve readability. Include inline links to helpful solution-related assets to build on information throughout the page.}
{In each headline, state an advantage gained from using the solution. What business challenge or pain point does it solve? If the benefit could apply to any solution, make it more specific.}
{In the description, expand on each headline. What business outcome will the solution deliver? How? What is the special differentiator that allows the benefit to happen?}
{It's not enough to say a solution has a benefit: provide concrete technical evidence. Use statistics if they are compelling, have a reliable source and directly support a point.}
Products
{The headline above should describe the section items, such as “Products.” Don’t use “Solutions” because the whole page is about solutions. Don’t use “Services” because they have their own section. This component is best for featuring an individual product or highlighting a product family and linking to the product family page. Here, describe the overall benefits of the product(s) mentioned in this section.}
{Specification}
{Product name}
{Product name}
{Product name}
{Spec name}
{Spec details for product}
{Spec details for product}
{Spec details for product}
{Spec name}
{Spec details for product}
{Spec details for product}
{Spec details for product}
{Spec name}
{Spec details for product}
{Spec details for product}
{Spec details for product}
{Type}
{Description}
{Product name(s)}
{Type}
{Describe the applications or benefits related to this type}
{Type}
{Describe the applications or benefits related to this type}
{Type}
{Describe the applications or benefits related to this type}
{Type}
{Describe the applications or benefits related to this type}
{The headline above should describe the section items, such as “Products.” Don’t use “Solutions” because the whole page is about solutions. Don’t use “Services” because they have their own section. Here, briefly introduce the overall benefits of the products.}
{Break this complex narrative component section up into multiple subsections if it helps to organize the content. Here, continue summarizing the product benefits, which can be organized according to subsection themes. Use inline links as needed.}
{Break this complex narrative component section up into multiple subsections if it helps to organize the content. Here, continue summarizing the product benefits, which can be organized according to subsection themes. Use inline links as needed.}
{The headline above should describe the section items, “Products.” Don’t use “Solutions” because the whole page is about solutions. Don’t use “Services” because they have their own section. This section intro is optional. Avoid marketing fluff.}
{In the item description, make the product’s tie to the solution topic abundantly clear. Start the description with a verb to keep it active.}
{Describe the product in terms of what it allows the client to technically do. Make sure the copy for each description is the same length.}
{If there’s room, mention product technology or benefits that are key to the content already discussed elsewhere on the page so the page feels cohesive.}
{Optional intro section can summarize services. Avoid marketing fluff.}
{In the item description, make the service’s tie to the solution topic abundantly clear. Start the description with a verb to keep it active.}
{Describe the service in terms of what its capabilities allow the client to do. How does the service help clients achieve goals? Make each description the same length.}
{Mention service capabilities or benefits that are key to the solution content already discussed elsewhere on the page so the page feels cohesive.}
{Use the section intro to summarize the services and overall benefits. Avoid marketing fluff.}
{Break this complex narrative component up into multiple subsections if it helps to organize the content. Here, continue summarizing the service benefits, which can be organized according to subsection themes. Use inline links as needed.}
{Break this complex narrative component up into multiple subsections if it helps to organize the content. Here, continue summarizing the service benefits, which can be organized according to subsection themes. Use inline links as needed.}
Use cases
{For each tab label, use a short, familiar phrase summarizing one way to use the solution. The label can repeat as the use case headline or be lengthened. In the body copy, describe how the use case works. Name specific products, services or technologies used.}
{For each tab label, use a short, familiar phrase summarizing one way to use the solution. The label can repeat as the use case headline or be lengthened. In the body copy, describe how the use case works. Name specific products, services or technologies used.}
{For each tab label, use a short, familiar phrase summarizing one way to use the solution. The label can repeat as the use case headline or be lengthened. In the body copy, describe how the use case works. Name specific products, services or technologies used.}
{There are three approaches for use case names: An active, benefit-oriented label starting with a verb (“Reduce security risks”); an adjective-noun benefit label...}
{...(“Predictive incident management”); and a noun label about an area of the business aided by the product (“Customer support”). Be consistent with...}
{...headline formats on a single page. In the body copy, expand on the use case name with details about how it works. Name specific features or capabilities used.}
{As space allows, briefly describe how the use case alleviates pain points and achieves specific client goals. Use cases can include industry-specific content.}
{You may include an optional text link below the body copy to a full use case page, demo, etc. Provide compelling information to inspire readers to click.}
{Be as specific as possible in the text CTA to meet accessibility requirements (for example, “Watch data modernization boost engagement 50% (00:00)”).}
Case study
{Optional section intro can summarize resources. Avoid marketing fluff.}
{If the resource title is too long or not descriptive enough, write a short headline in sentence case that better summarizes it. Try to use the same format for all resource headlines in this section.}
{In the body copy, describe the resource in terms of what the client gets. Make it clear how the resource relates to the solution. Start with a verb ("Explore," "Discover," "Watch," etc.)}
{Include more details as space allows. Make sure the copy for each item description in the section is the same length. Each resource link should lead directly to the resource.}
{Describe the related solution. Make it clear how it’s related to the solution discussed on the page. Highlight client benefits that would inspire readers to click. Be specific about related product technologies or service capabilities involved.}
{Describe the related solution. Make it clear how it’s related to the solution discussed on the page. Highlight client benefits that would inspire readers to click. Be specific about related product technologies or service capabilities involved.}
{Describe the related solution. Make it clear how it’s related to the solution discussed on the page. Highlight client benefits that would inspire readers to click. Be specific about related product technologies or service capabilities involved.}
Footnotes
{1 Report title, Publisher, XX Month XXXX}