The document discusses a strategy for understanding customer problems by involving the development team in customer interactions. It suggests creating a podcast to share customer insights and generating content like blog posts to disseminate the learnings. Key steps include recording interviews, trimming them for clarity, and using various tools for publication.

1. Gettheteamto
understandthe
problemthrough
theeyesofusers
Madelen Arnesdotter, Brisk

2. HowIgothere
@mArnesdotter
FOAP Brisk
Support
Customer Success
Marketing
Customer Success
enterprisemarketplace

3. Theissue?
@mArnesdotter
Customer facing Development
How?Why?

4. Theideal
@mArnesdotter
Development talking to customers
- stressing the customer
- costs a lot of time
- not all developers “enjoy” customers…

5. Thesolution
@mArnesdotter
Talk to customers and get everyone to listen

6. How?
@mArnesdotter
Record a podcast so everyone can listen

7. Before
@mArnesdotter
Ask anyone with “social signals”
Give them an incentive, “a blog post about you”
Research and plan

8. During
@mArnesdotter
Auto record call (ask if ok, they will review)
Open questions that leads to your thesis
Dig! Why / tension / conflict / current solution

9. After#1:Learning
@mArnesdotter
Trim/Edit - But not to much
Publish as an internal podcast

10. After#2:Blogpost
@mArnesdotter
Find angles / top list
Transcribe
Write post
Get ok
Publish + mention -> Cred

11. Toolsandprocess
@mArnesdotter
2. Interview
1. Ask
3. Auto-record
4. Trim
5. Podcast
7. Angle
6. Transcribe
8. Copywriter
9. Wordpress
eCamm: $20
JustCast: $5/mo
Rev: $1/min
$100-400 / post

12. Win
@mArnesdotter

13. Thanks!
@mArnesdotter
@brisk_io