Activity
Mon
Wed
Fri
Sun
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
What is this?
Less
More

Memberships

JUSTANOTHERPM

994 members • Free

9 contributions to JUSTANOTHERPM
AIPMA Week 4 Activitiy Submission
This is where you submit your work for the three Module 4 activities. Reply to this post with your submissions. What to submit: Activity 1 — The PM Decision Audit Your 4-section diagnosis memo (300–500 words). Include all four sections: what the user expected, what the system did, root cause, and recommended fix. Activity 2 — Design the Invisible Decisions Your answers to all 5 PM decisions for the Spotify "Why This Song?" feature. Be specific — "it should be smart" doesn't count. Activity 3 — The Trade-off Debate Your synthesis paragraph(s). Complete the sentence for each dimension: "Notion AI's approach is better when ___. Gemini's approach is better when ___." How to submit: Make a copy of the google doc in the original post. Add your answers to it. Reply to this post, and include a link to your doc. Peer review (Activity 1 only): After you submit your diagnosis memo, read two other students' submissions and reply to their comment with your peer review. Do you agree with their root cause? Would their fix work? Did they catch something you missed? Drop your submissions below 👇
1 like • 24d
My submissions for Activity 1 and 2.: https://docs.google.com/document/d/1ubKrJJ6P_ObddwEeeiNAMkOXxZGfUhDI9UDzN8QWjYU/edit?usp=sharing
AIPMA | Week 3 Activity | Coh 001
Before you build AI, you define what "right" looks like. That's a golden set. Your task: Create 10 test cases for a travel itinerary chatbot. Define the user, their message, and exactly what the AI should (and shouldn't) do. Full brief with product context and template linked in the above post. Drop your submission link in the comments 👇
2 likes • Feb 13
Here is my submission: https://docs.google.com/document/d/10ff8Rk3oukdYm0zbmmTA-UtXlHjK47P7lUBzPIdcFl8/edit?usp=sharing
Week 2 Activity
This week you've got 5 activities that put everything from Module 2 into practice: 1. Fix the Prompt — Take broken prompts and rewrite them using the 5 Elements framework 2. Diagnose the Failure — Figure out why an AI product is giving bad output (hint: it's almost never the model) 3. Design the Context — Map out all 6 context components for a real product scenario 4. Classify the Approach — Decide whether a feature needs a simple prompt, RAG, an agent, or fine-tuning 5. Write a System Prompt — Write a production-quality system prompt from a product brief, then test it live This Google Doc has all 5 activities. Here's what to do: → Make a copy of the doc → Work through the activities → Link your completed copy as a comment on this post
1 like • Feb 8
Week 2 Activity - my attempt attached (Sorry - will do the Google doc next time). I was a bit confused in Activity 3: Design the Context. Hence answered the first one (Scenario A) only. Overall, it was a fun, though a bit intense, activity.
AIPMA | Module 1 Activity | Coh 001
Please share a document with the LLM's name, prompt and the learning summary of session. Please include a visual (optional) Also share in the comments below how would you define "good quality" in this case, and how would you measure success of the "Online classes learning summariser" feature
1 like • Jan 27
Quality: These are some facets to test quality - accuracy, completeness, readability etc. To test on these, I’ll feed 2 different responses to an AI tool to compare: 1. What key learning did a response miss? (Completeness) 2. What key learning did a response have in contradiction to another response? (Interpretation issues / hallucinations) 3. Rate the responses on complexity of language (not very sure about this as mostly all models do well on readability - so this could be ignored). Manual testing is another option. Asking a manual reader to read 2 responses and compare. Success: Thumbs up, Copy, Download, fewer follow on prompts for revision. Preference for detailed vs short (quick, actionable insights) summaries is subjective. The nature of revisions sought by the users can reveal that preference. Better still, give the users the option to select that upfront. End the summary with feedback questions like - Was this summary helpful? Did I miss anything important?
Week 2 Activity 1: What tech stack does your product need
Submit your answer here. Keep it simple. Just explain in simple English. Be sure to call out "why" you think you need or don't need a specific aspect in your product. Let's go 👇
0 likes • Jan 21
@Phil L Great problem to solve and its akin to bringing a human touch to AI. The difficult part I reckon will be to get personas of hiring team.
0 likes • Jan 24
@Manasa Shetty thanks for the suggestions.
1-9 of 9
Akshun Gulati
2
8points to level up
@akshun-gulati-5248
Fintech co-founder, building next gen loan origination software for banks and NBFCs in India.

Active 18h ago
Joined Dec 31, 2025
Powered by