Learning path · Level 1 · Tutorial 2

Identifying AI Tasks and the Products Around Models

Identify the task an AI feature performs and distinguish its underlying model from the application people interact with.

  • Level: Beginner
  • Duration: 10 min
  • 7 steps
Start tutorial Back to the path
Identifying AI Tasks and the Products Around Models

What you will go through

  1. Prediction: Estimate an Outcome Recognize Prediction features by the unknown outcome they estimate. 1 min
  2. Classification: Assign a Category Distinguish category assignment from outcome estimation by examining the expected output of a ShopGuide feature. 1 min
  3. Recommendation: Suggest Relevant Options Recognize recommendation as selecting or ranking relevant options, using ShopGuide’s notebook suggestions. 1 min
  4. Generation: Produce Content 1 min
  5. One Product, Several AI Tasks 2 min
  6. The Model Is Not the Whole Product Separate an output-producing model from the product experience that surrounds it, using ShopGuide, ReadNext, and Model Cedar. 2 min
  7. Apply the Task and Product Map Apply all four AI task labels to a new product scenario and separate the product experience from its named drafting model. 2 min

What you will learn

  • Classify described AI features as prediction, classification, recommendation, or generation, explaining the expected output.
  • Identify an application that combines more than one AI task rather than forcing the whole product into one category.
  • Distinguish a model's role in producing outputs from the interface and surrounding functionality provided by a product.
  • Explain why a model name and a product name do not necessarily describe the same thing.

Before you start

  • Distinguishing AI, Machine Learning, and Generative AI

Step 1 of 7

Prediction: Estimate an Outcome

Recognize Prediction features by the unknown outcome they estimate.

Identify the intended output

Start with the output

To identify an AI feature’s task, start with one question: What is this feature intended to produce from its input?

A Prediction feature estimates an outcome that is not yet known. Its output is an estimate, such as a duration, amount, or time.

For example, ShopGuide receives delivery details and estimates how long delivery will take. The feature’s purpose is the estimate—not the order details it received.

A prediction feature in ShopGuide

Diagram showing delivery details flowing through a Prediction feature to an estimated delivery time of 3 days.

delivery details → Prediction → estimated delivery time: 3 days

Read the delivery estimate

Estimate versus observed result

An estimate is different from an observed result.

When ShopGuide says 3 days, it is estimating the delivery duration before the delivery outcome is known. After the package arrives, the actual duration is an observed result.

Prediction is not limited to events that have not happened yet. A feature can estimate an unknown outcome even when part of the situation has already happened—for example, after an order has been shipped but before it arrives.

Example

Worked example

Feature: ShopGuide receives delivery details for an order and displays an estimated delivery time.

Task: Prediction

Expected output: estimated delivery time: 3 days

The input helps form the estimate. It is not itself the predicted outcome.

Tip

Keep the label practical

The labels used in this tutorial describe a feature’s practical purpose. They are not names for four separate, mutually exclusive model technologies. Later steps compare other purposes; for now, focus on whether the feature estimates an unknown outcome.

Practice: identify the output

Find the predicted outcome

A navigation feature receives a route and current traffic details. It estimates when a driver will arrive. What is the feature’s expected output?

Step 2 of 7

Classification: Assign a Category

Distinguish category assignment from outcome estimation by examining the expected output of a ShopGuide feature.

Notice the expected output

From a review to a category

A feature performs Classification when its intended output is a category from a defined set. Start with the output: if the feature assigns a label such as a sentiment category, it is classification.

ShopGuide can read a customer review and assign one of 3 categories: Positive, Neutral, or Negative. The feature is not estimating how long something will take; it is selecting the category that describes the review.

Two different output types

A comparison shows a customer review receiving one of three sentiment categories, while delivery details produce a 3 days estimate.

A category is an assigned label; 3 days is an estimated outcome.

Choose by purpose, not by timing

Classification versus Prediction

Both features may use information about an input, but their visible purposes differ. Use the more specific task label that matches what the feature is meant to return.

Identify the task from the output the feature is designed to provide.
Feature inputTaskExpected output
Customer review textClassificationPositive, Neutral, or Negative
Delivery detailsPredictionestimated delivery time: 3 days

Tip

Use the specific label

Sometimes people describe assigning a label as “predicting a label.” That is a broad use of the word prediction. In this tutorial, when the output comes from a defined category set, use the more specific label Classification.

Do not decide from the topic alone. A review can be classified today, and a delivery estimate can concern an outcome not yet observed. The deciding clue is the intended output: category or estimate.

Practice: categorize the features

Match task to output

Match each feature description to its task and expected output.

Tap an item and then its matching pair.

Step 3 of 7

Recommendation: Suggest Relevant Options

Recognize recommendation as selecting or ranking relevant options, using ShopGuide’s notebook suggestions.

Recommendation selects options

Suggestions for a shopper

A Recommendation feature selects or ranks options that may be useful in a person’s context. Its visible purpose is to suggest choices—not to estimate one outcome and not to assign one category.

Ask: What does the feature give the shopper? If it gives one or more suggested items, the task is Recommendation.

ShopGuide can use a shopper’s stated interests to suggest notebooks from its available options. The output may be a single suggestion or a ranked list.

From context to suggested options

A diagram showing shopper preferences and available notebooks leading to three notebooks arranged in ranked order.

A recommendation selects or ranks options from the available notebooks based on the shopper’s context.

Example

Worked example

ShopGuide feature

stated interest: compact notebooks for a trip → Recommendation → Pocket Notebook, Travel Notebook, Desk Notebook

The three notebook names are suggestions in ranked order. They are not labels applied to the shopper or to a notebook.

A recommendation system may use estimates internally, but identify the feature by its visible result: it helps the shopper choose among options.

Practice: identify the purpose

Check the task

True or false: A ShopGuide feature returns a ranked list of notebook options. Because the list contains names, the feature’s task is Classification.

Apply the distinction

Choose the correct task

A shopper says they want a small notebook for travel. ShopGuide shows, in order: Pocket Notebook, Travel Notebook, Desk Notebook.

Which explanation is correct?

Step 4 of 7

Generation: Produce Content

Recognize a generated result

Generation creates content

A feature performs Generation when its purpose is to produce new content from an input.

In ShopGuide, recipient details can lead to a drafted gift message:

recipient details → Generation → gift-message draft

The output is composed for this request. It is not a label from a fixed set and not a selection from existing notebook options.

Three different purposes

A diagram contrasts composing a new gift message with assigning a review category and highlighting an existing notebook option.

A gift-message draft is Generation. A review category is Classification. A highlighted existing notebook is Recommendation.

Look beyond the words

Text can serve different tasks

Generation can produce text, images, audio, or video. Here, focus on text: ShopGuide drafts a gift message.

Do not identify a task only by what appears on the screen. A category label such as Positive is text, but its purpose is category assignment. A notebook name is also text, but its purpose can be to suggest an existing option.

Purpose determines the task

Compare each feature by its intended output, not by its display format.

Feature-level task map for ShopGuide
InputTaskExpected output
recipient detailsGenerationgift-message draft
review textClassificationPositive
shopper interestsRecommendationTravel Notebook

Tip

A useful check

Ask: “Is this feature composing content, assigning a category, or choosing relevant existing options?” The answer identifies the task.

Practice: identify the purpose

Match purpose to task

Match each ShopGuide feature to its task label.

Tap an item and then its matching pair.

Step 5 of 7

One Product, Several AI Tasks

See the product as a set of functions

Start with the features

A product can offer several AI-powered features, and each feature can have a different task. Do not force the whole ShopGuide product into one label.

In this scenario, ShopGuide explicitly states that its delivery estimate, review-sentiment label, notebook suggestions, and gift-message draft are AI-powered. A visible interface alone would not prove that a feature uses AI; the description supplies that information here.

Four features inside one product

An illustrative ShopGuide dashboard separates delivery estimation, review labeling, notebook suggestions, and gift-message drafting into four feature cards.

Each card represents a feature. The task label belongs to that feature, not to ShopGuide as a whole.

Map input to task to output

Feature-level task map

Decompose the product by tracing each feature from its input to its intended output.

ShopGuide has multiple task types because its features have different intended outputs.
InputTaskExpected output
Delivery detailsPredictionestimated delivery time: 3 days
Review textClassificationsentiment category: Positive, Neutral, or Negative
Shopper's stated interestsRecommendationsuggested notebooks: Pocket Notebook, Desk Notebook, Travel Notebook
Occasion and recipient detailsGenerationgift-message draft

Check the task labels

Practice: identify each feature's task

Match each ShopGuide feature to its task.

Tap an item and then its matching pair.

Explain the whole product

Apply the complete task map

Analyze ShopGuide as a multi-feature product. For each of its 4 features, write the input, the Task: label, and the Expected output:. Then explain why calling ShopGuide only a recommendation tool is incomplete.

Write at least 250 characters (0/250).

Step 6 of 7

The Model Is Not the Whole Product

Separate an output-producing model from the product experience that surrounds it, using ShopGuide, ReadNext, and Model Cedar.

Separate the application from its component

Two different roles

A product is the user-facing application. It can provide screens, input controls, settings, saved history, and connections to information or other software.

A model is an underlying component that receives an input and produces an output. It is not the whole application.

Product: ShopGuide is the illustrative shopping product that a person uses.

Model: In the stated scenario, Model Cedar receives a gift-message request and produces a draft for ShopGuide’s gift-message feature.

A model inside a product

A component diagram showing Model Cedar as one component inside the larger ShopGuide product, with input controls, settings, saved history, and shopping-information connections around it.

Model Cedar produces the draft for the stated feature. ShopGuide provides the surrounding experience.

A model can be shared

Names do not tell the whole story

The same model can appear in different products. Conversely, one product may use several models. Do not assume that a named model powers every feature unless product information explicitly says so.

Two products, one stated model

These are illustrative product experiences. The stated shared model applies to the drafting feature shown in each row, not automatically to every feature in either product.

Sharing a model does not make products identical.
ProductStated drafting featureModel in the stated scenarioSurrounding functionality
ShopGuideGift-message draftModel CedarShopping inputs, settings, saved history
ReadNextDiscussion-question draftModel CedarReading controls, saved history, library connections

Do not infer the model

Check your evidence

True or false: A product name or screenshot alone reliably identifies its underlying model.

Apply the component map

Apply the component map

Using the component diagram you studied, match each statement to its correct conclusion.

Tap an item and then its matching pair.

Step 7 of 7

Apply the Task and Product Map

Apply all four AI task labels to a new product scenario and separate the product experience from its named drafting model.

Read the transfer scenario

ReadNext feature brief

Apply the task map to a new scenario. In this illustrative brief, every function below is explicitly described as an AI-powered feature in the reading product ReadNext.

  • Demand outlook: current reservations and calendar information → Task: Prediction → Expected output: a forecast of library holds next week.
  • Review tone: a reader review → Task: Classification → Expected output: Positive, Neutral, or Negative.
  • Book picks: a reader’s interests and reading history → Task: Recommendation → Expected output: suggested books to consider.
  • Discussion starter: a selected book and audience → Task: Generation → Expected output: drafted discussion questions.

One product, a named drafting model

A diagram of the ReadNext product with four AI features. Only its discussion-question drafting feature connects to Model Cedar.

ReadNext presents the features to its users. Model Cedar is explicitly named only for the discussion-question drafts in this scenario.

Name the layers precisely

Product: ReadNext is the user-facing reading application. Its interface can present features and provide surrounding functionality for readers.

Model: Model Cedar is the underlying component explicitly named for producing ReadNext’s discussion-question drafts.

ShopGuide uses Model Cedar for gift-message drafts. Shared use of one model does not make ReadNext and ShopGuide the same product: they serve different users through different interfaces and features. The brief does not name the models, if any, used by ReadNext’s other features.

Quick task check

Map features to tasks

Match each ReadNext feature to its task label.

Tap an item and then its matching pair.

Final application

Build the complete map

Create a concise map from the earlier ReadNext brief. Include all 4 features with their Task: label and Expected output:. Then identify the product and the named model with their stated roles. Finally, explain why the two products that share that model for a drafting feature are not identical.

Write at least 300 characters (0/300).

Wrap up

Summary

Key takeaways

  • Prediction estimates an unknown outcome.
  • Classification assigns a category from a defined set.
  • Recommendation suggests or ranks relevant options.
  • Generation produces new content from an input.
  • Task labels describe features, not an entire product.
  • A product is the user-facing experience; a model is an underlying component that produces outputs.
  • A model can serve drafting features in more than one product without making those products identical.

Tutorial complete

Congratulations! You completed: Identifying AI Tasks and the Products Around Models

You can now identify AI tasks at the feature level and distinguish a product from the model it uses.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate