Draft the process for technical discovery

[lizpearl]

Issue description

Draft a technical discovery process so developers who have not participated in this phase can know what to expect. The goal here is to include learnings from our latest technical discovery and then use this draft for the next time technical discovery is needed.

Acceptance criteria

• [ ] Define deliverables of the technical discovery process
• [ ] Outline the discussions that should take places and who is responsible for scheduling/initiating them (kickoff, check in, architecture review, etc)
• [ ] Provide an example (if possible)
• [ ] Add the document in our shared drive and attach link to this issue

Additional context

No response

Links to other issues

No response

[h-m-f-t]

I think this is an important task, but I wonder if we have enough team experience to define a process. It almost seems like what we need is something lean that reflects what we learned from the recent discovery, with maybe some things to think about in defining a future process. I worry that defining that process now might be heavier than we need, and that creating it requires a few more iterations.

@lizpearl, do you think that's^ reflective of this issue, or do you think we need more now?

[lizpearl]

@h-m-f-t Ok that's fair that we probably don't have enough team experience to make this a process. I updated the ticket to specify that it's a draft to be used for learning for the next time we do technical discovery.