AI @ MCS

Playbooks

Requesting a TD Study

How to ask TD to investigate a technology question or evaluate an approach for your team.

Audience  Product teams, engineering leads

A TD study is a time-boxed investigation (typically 2–4 weeks) that produces a written recommendation. Use it when your team faces a decision that hinges on unfamiliar technology, or when you want an independent read on a tradeoff.

When to request a study

  • You’re choosing between two architectural approaches and need evidence, not opinion.
  • You want to know whether a specific tool or pattern will work at Thales scale before committing.
  • You’ve hit a technical wall and need outside expertise.

Studies are not appropriate for well-understood problems, or for work that belongs inside your own team’s backlog.

How to request

  1. Write a one-page brief. Include: the decision you’re trying to make, the constraints you’re working within, and what “good enough” looks like.
  2. Email td@thalesgroup.com with the brief attached, or open an issue on the TD GitLab project with the study-request label.
  3. Schedule a 30-minute scoping call. TD will confirm whether a study is the right format, or suggest an alternative (office hours, an existing entry, a playbook).
  4. Agree on scope and timeline. TD will confirm within 5 business days. Most studies are completed within 3 weeks of kickoff.

What you’ll receive

A structured markdown document covering: background, methodology, findings, and a clear recommendation. The document is published to this catalog as a study type entry and linked back to your team.

What you won’t receive

TD studies don’t produce code, prototypes, or slide decks. If you need a proof-of-concept, that’s a separate conversation.