1. Technology Architecture intermediate Multiple choice

    A language runtime used by 180 of 240 services leaves vendor support in 14 months. Services are owned by 40 teams with their own roadmaps, and the upgrade is mostly mechanical but breaks in about 15% of cases. Which approach gets the estate upgraded?

    3 min answer lifecycleend-of-lifemigrationfunding
  2. Technology Architecture advanced

    An enterprise's technology architecture standards assume commodity compute. A new workload requires specialised hardware, specific interconnect and a different operational model. How should standards handle this?

    2 min answer technology-standardsexceptionsspecialised-hardwarenvidia
  3. Technology Architecture beginner

    An internal team and a packaged-software vendor both pick the same message serialisation format this quarter. Two years later the internal team replaces it in a single sprint. The vendor still supports it and expects to for another decade - an ERP vendor in SAP's position has customers whose 12-year-old integrations must keep working across a major release. Nothing about the technology differs. What makes the same choice a different decision for each of them?

    3 min answer technology-architecturereversibilitybackward-compatibilitydependents
  4. Technology Architecture intermediate

    An organisation's technology choices from five years ago now constrain its options. How should technology lifecycle be managed rather than discovered?

    2 min answer elasticlifecycledeprecationupgrade
  5. Technology Architecture intermediate

    How would you decide which technologies in an estate need attention first?

    2 min answer obsolescencelifecycleriskstandards
  6. Technology Radar intermediate

    An organisation maintains a technology radar that nobody consults before choosing tools. What makes a radar useful rather than decorative?

    2 min answer druvaradarstandardsgovernance
  7. Technology Radar intermediate

    An organisation publishes a technology radar and teams ignore it. What makes a radar influence decisions?

    2 min answer technology-radaradoptionevidencegovernance
  8. Technology Radar intermediate

    How can a technology radar function as lightweight governance, and what makes it degrade into a list nobody consults?

    3 min answer technology-radargovernancestandardsadoption
  9. Technology Radar intermediate

    Thoughtworks has published its Technology Radar since 2010 and now twice a year - volume 33 appeared in November 2025 - sorting technologies into adopt, trial, assess and hold from blips submitted by client project teams and curated by an internal group. An enterprise copies the artefact: the same four rings, a page per technology, published quarterly by a central architecture team of five. Two years on, teams do not consult it before choosing tools. What did the copy leave out, and where would copying the original be a mistake?

    3 min answer technology-radarthoughtworksgovernanceevidence
  10. Technology Radar intermediate

    What is a technology radar for, and what makes one useless?

    2 min answer technology-radarstandardsholdgovernance
  11. Technology Standards intermediate Multiple choice

    A platform company wants engineering standards without slowing autonomous teams. Where should standards be mandatory, and where should they be defaults?

    2 min answer standardsautonomypaved-roadgovernance
  12. Technology Standards advanced

    An organisation has grown from 200 to 2,000 engineers and each team chose its own queue, cache and database. What criteria decide which technologies become paved-road defaults, which are tolerated, and which are retired — and how is the migration funded?

    3 min answer paved-roadstandardsrationalisationmigration