Welcome to the Content Design assessment.

This is your opportunity to show off your content

design skills and get a glimpse into the day-to-day work of content designers at IBM. This
assessment is divided into four parts. We’re conscious of the time investment for you, so we suggest
that you spend no more than 60 minutes in total. Of course, you might not have all the information
that you typically have as a project team member or feel like you need to complete all parts. That’s
fine – just be sure to note the questions you would ask and the assumptions you’re making.

Part 1: Task writing

Instructions: Imagine you’re writing a book of life skills for teenagers with short attention spans.
Write instructions for making the perfect cup of tea or coffee. Be sure to include an introductory
paragraph that explains the importance of the perfect cup of tea or coffee without using the word
important.
Part 2: UI copy review

Instructions:

Imagine that you’re part of a design team working on a product called Vegetation Management. The
product uses AI and advanced analytics to help utility companies assess the state of vegetation
across their service territories. They rely on vegetation management to determine where trees need
to be trimmed around their utility lines to avoid power outages.

Your team is working on a new list view feature that allows users to see the vegetation status across
each region, filter their data based on specific parameters, and then export the data to share it with
their teams. Recently, your team got feedback from your users that the list view has all the data they
need, but they get lost in all the new terminology and can’t always find what they’re looking for.

Using the following persona information and your content design knowledge, how would you
improve the list view experience? How would you approach these pain points from a content
design perspective? What questions would you ask and what assumptions would you make? Feel
free to suggest specific changes that you would make.

Persona information Questions and

assumptions
Vegetation Management list view

List all the changes that you would make in this section or tag sections of the UI with specific
comments.
Part 3: Onboarding tour

Instructions: Now, it’s time to think about the getting started experience for a Vegetation Manager.
The tour would start from the map view within Vegetation Management where Rudy can zoom in
and out of the map to inspect different service areas. From the map, he can also hover over or click
on a specific area to get more information.

What would you include in a getting started tour experience for first-time users of this feature? How
many steps would you include and what would the sequence look like? Consider what Rudy needs to
know when he first uses the product. For this activity, focus more on the content and less on the
implementation or tool that you would use to build the tour.

Persona information Questions and

assumptions
Vegetation Management map view

Add the tour outline that you would suggest in this section or tag sections of the UI with
comments specifying the tour step number and specific content that you would add.
Part 4: Review technical documentation

Instructions: For this activity, we’re shifting focus to a different product and persona. You are asked
to improve previously written getting started content for the Maximo Health product. The persona
for this content is Marcia, the reliability engineer. This content is part of a larger quick start tutorial
that is designed help Marcia configure scoring so that she can do her job of monitoring and
improving asset reliability. Edit the text directly and note any questions you have or assumptions you
are making.

Persona information Questions:

1. Example
for how
can we
derive the
custom
formula
for
Criticality
score.

Assumptions:
1. The lowest
possible
score is
always
zero; the
highest
possible
score is
always
100.
2. Ranges
are used
for health
scores
only and
for scoring
elements
that are
related to
health
scores.

Edit the text directly:

You can use the Scoring Tab to configure the user's performance, condition indicators and to view
the root cause of failure for objects, such as Assets. You can configure different types of scores
such as health, criticality, and risk scores. Below table describes the purpose of each score:
On the Scoring Tab, scores can be configured to reflect the user’s performance and condition
indicators, and reveal the root cause of failure for objects, such as Assets. Many various different
types of scores can be configured, like health, criticality, and risk scores.

Type of Score Enables you /Purpose/Use Calculation

Health View the description of the Value ranges from zero to
overall condition of an Asset. 100.
Note: Ranges can be
categorized to define the
health condition of an Asset.
Criticality Determine which Assets are Derived from a custom
prioritized for maintenance or formula.
funding to prevent failure.
Risk Describe the risk which Assets Default formula: [(100 -
pose due to disrupting the health score)/100) x Criticality
user’s operations through score]
failing or requiring Note: You can customize
unexpected maintenance. formula to calculate risk.

Health scores enable the description of the overall condition of an asset. A health score
can be any value between zero to 100 and you can configure ranges to determine the
condition that each numerical health score indicates. Criticality is used to determine
what assets are prioritized for maintenance or funding to prevent failure. A criticality
score is calculated from a custom formula. Risk can describe the risk which Assets pose
to disrupting the users operations through failing or requiring unexpected maintenance.
This is the default formula ((100 - health score)/100) x Criticality score but a new formula
can be configured to customize how risk is calculated.

Ranges can be thought of as categories of health conditions, and the numerical scores,
icons, and colours that indicate those conditions. Ranges are used for health scores only
and for scoring elements that are related to health scores. The lowest possible score is
always zero; the highest possible score is always 100.