Choose a product you use daily. What is the functional, emotional, and social job it does for you? How does the system’s architecture reflect each dimension?
Take an internal API in your current system. Does it expose what the system does, or what users want to accomplish? Rewrite the endpoints in job-oriented terms and compare the two designs.
The chapter argues that “write faster,” “write better over time,” and “not lose my work” are three different jobs that require three different architectures. Apply the same analysis to a system you work on. How many distinct jobs does it serve? Does the architecture reflect that number?
A team wants to add a feature to their product. Walk through how you would identify the job the feature serves, determine whether it is a new job or an extension of an existing one, and evaluate whether the current architecture can serve that job without structural changes.