About Trynn
Why I built Trynn
I wanted a clearer way to plan my own training and understand why each session was there.
Training and racing in triathlon
Building and delivering software
Learning to coach myself
For the past few years, I’ve coached myself. That meant making the decisions a coach would normally help me think through. What should I focus on this week? How much can I take on? What should change when life gets in the way?
I read books, articles and blogs, listened to podcasts, and watched training videos. I followed coaches and athletes at both elite and amateur levels. Then I tried ideas in my own training and paid attention to what I could actually put into practice, week after week.
Making the plan easier to understand
I’ve spent more than 25 years developing and delivering software, from writing it as a software engineer to leading teams as head of engineering. Building Trynn gave me a way to bring that experience into my training.
I wanted to see how a workout fits into the week, how the week fits into the season, and what a proposed adjustment would change. I built Trynn for self-coached athletes who want that same visibility and want to make the final call on their training.