Teaching product counsel judgment means giving learners a structured way to assess a situation, make a recommendation, explain their reasoning and revisit the call when facts change.
That is the practice I want to make more explicit.
A learner should have opportunities to identify the relevant facts, apply the law, weigh the consequences of available options and communicate what should happen next. Feedback should show where the reasoning was strong, which assumption needs examination and what the learner should try again.
A useful starting point is a product situation small enough to work through carefully.
Start with a decision someone actually needs
Consider this illustrative training scenario.
It is Tuesday. A team plans to launch an AI support assistant on Friday. During internal testing, the assistant repeatedly promises refunds beyond the company’s approved terms. Engineering says it can keep generated replies in draft form for a support agent to review. Product needs your recommendation by 3 p.m.
What would you recommend?
Before answering, identify what matters to this decision. What refund rights and customer commitments apply? What does the assistant actually say? Can an agent check every reply before it reaches a customer? Has Engineering tested the sending controls? Who has authority to approve a release?
These questions give the legal analysis a concrete purpose. They connect the available facts to the action the team is considering.
They also make uncertainty visible. “Engineering says it can” describes a proposed control. The recommendation still needs evidence that the control works.
Make the recommendation usable
A practice exercise should ask the learner to produce advice that a colleague could act on.
In this scenario, one possible recommendation is:
“Hold automated customer replies. Consider a limited, staff-reviewed pilot only after we confirm the applicable refund requirements and customer commitments, verify that agents can check every reply before sending, and test the controls. Support owns the review plan, Engineering owns the sending controls, and Product records the release decision. We reassess when those conditions are evidenced.”
The recommendation identifies an immediate action and the conditions for considering another path. It also gives the team concrete work to do.
The reasoning deserves examination. Which customer harm is the recommendation addressing? What makes the proposed review meaningful? Which assumption could invalidate the plan? What would require escalation?
Other recommendations may be defensible on different facts or assumptions. The learner should be able to explain those differences clearly.
Teach a usable framework, then practice applying it
Foundational instruction should give learners something they can carry into the exercise.
A learner may need help recognizing the product’s lifecycle stage, separating an observed problem from its cause, prioritizing a risk or choosing the right way to communicate advice. Introduce the relevant framework, explain its purpose and demonstrate its use.
Then ask the learner to apply it to the scenario.
For the support assistant, the learner should recognize that the feature remains in internal testing. That matters because the team still has an opportunity to change the release plan before exposing customers to the problem.
The learner should also distinguish the observed refund promise from the proposed mitigation. Naming “human review” does not establish that the review is workable. Someone needs the capacity, information and authority to perform it.
The framework becomes useful when it changes what the learner asks, recommends or communicates.
Change one fact and revisit the call
Now add a fact: Support cannot review every generated reply before Friday.
What changes?
The proposed pilot depended on that review. The learner should revisit the plan and explain the consequence.
A revised recommendation could be:
“Keep the assistant in internal testing and continue using the existing support process. Revisit the pilot when the team can demonstrate a workable review process and tested sending controls.”
The learner should explain the tradeoff. The company gives up the planned Friday release while it addresses the conditions needed for customer use.
This is a useful moment to examine consistency. The recommendation should respond to the changed fact. The learner should be able to name the dependency that failed and explain why it matters.
Practice can also introduce facts that support proceeding. The exercise should test whether the learner can update their reasoning in either direction.
Give feedback that improves the next attempt
Useful feedback should point to something the learner can examine and change.
For example:
“You made the pilot conditional on staff review. Your answer still needs to identify who can perform that review and what evidence shows it is feasible. Revise the recommendation to address those points.”
That gives the learner a specific task.
Feedback should examine the facts used, legal accuracy, assumptions, prioritization, feasibility and communication. It should explain how those elements affected the recommendation.
The learner then needs another attempt. Ask for a revised message to Product, a short explanation for a legal leader or the question they would put to Engineering.
A disagreement with an example answer should lead to examination of the reasoning. A well-supported alternative deserves careful consideration. A confident answer built on an invented fact needs correction.
The goal is to help the learner understand what to carry into the next situation.
Build practice into professional development
A legal team or classroom can begin with one bounded scenario and one learning objective.
Give participants the same facts. Ask each person to write a recommendation, identify the assumption on which it depends and explain what would change their view. Discuss the reasoning, introduce a new fact and ask for a revision.
Adjust the support to the learner’s experience. Someone entering product counsel work may need a worked example and a clearly explained framework. A more experienced lawyer can be asked to handle competing demands, defend a tradeoff and communicate under pressure.
Then ask a transfer question: where else could this pattern appear?
The same questions about an untested control could arise in a location-sharing feature, a marketing review or a new customer onboarding process. The learner should be able to recognize the pattern beyond the original exercise.
Frankie is designed to help lawyers practice product counsel judgment through frameworks, realistic scenarios and structured feedback. The purpose is to make the reasoning available for examination and improvement.
That is the opportunity I want legal educators and legal leaders to take seriously: give lawyers a place to practice the recommendation, examine the assumptions and improve the next attempt.
Frequently Asked Questions
What is product counsel judgment?
Product counsel judgment involves applying legal analysis to a specific product situation, prioritizing what matters and recommending a course of action with clear assumptions, conditions and responsibilities.
How can lawyers practice product counsel judgment?
Use a realistic scenario, make a recommendation, explain the reasoning, receive specific feedback and revise the answer. Foundational instruction can introduce the framework the learner will apply.
What makes feedback useful?
Useful feedback identifies the fact, assumption or reasoning step that affected the recommendation. It gives the learner a specific improvement to make and an opportunity to try again.
What is Frankie designed to help learners do?
Frankie is designed to help lawyers practice product counsel judgment through frameworks, realistic scenarios and structured feedback. Legal accuracy and professional responsibility remain essential throughout.
Explore more product counsel judgment articles on Product Law Hub.
