Recently, we sat in a retreat room in the US, learning about a product we've worked with for 2.5 years but had never seen "from the inside" like this. It's strange how different something feels when you go from screens and calls to actually being there.
Understanding the Why Behind the Product
Over the years, we've worked with Timely as part of our roles at Procedure Technologies. In that time, we'd built features, closed tickets, joined calls, and watched the product evolve, always through a screen. We understood what we were building. What we didn't fully have was the why.
That changed in the retreat room. Watching the Timely team talk about their vision, their roadmap, and the thinking behind features we'd only ever known as line items on a sprint board, it recalibrated how we think about the work we do together. Suddenly, the "why" behind decisions wasn't something we were told after the fact. We were in the room while those decisions were being shaped.
Timely is an education technology company, and most of the team's day-to-day work is with schools and schedulers. They're the people who actually use the product and live with its decisions. Until now, much of that world reached us secondhand, through requirements, feedback, and tickets.
Meeting the team in person gave us the full picture. We got to hear directly how schedulers think, what they're juggling, and what a good solution really looks like from their side. We also saw the impact the product has on the schools using it.
A feature feels different once you understand the problem it solves for the person on the other end.
Having a Say in Product Decisions
That's really the heart of what this trip changed for us. Understanding the decisions that go into the building phase and actually having a say in those conversations rather than just executing on what came down the pipeline made us see our own roles differently.
At the retreat we got to ask why a feature mattered, question it, and help shape it. After all this time working with Timely, we realised our work was more than tasks completed, and that the team saw it that way too.
What Meeting in Person Gives a Remote Team
Until then, the Timely team had mostly been faces on a screen to us.
There were quieter moments too, and in some ways, those taught us just as much as the structured sessions. Conversations over coffee. Casual chats between sessions. The kind of small talk that never happens naturally over a scheduled call.
Meeting the team in person gave us the chance to connect in a way that video calls simply can't replicate. We got to see how people actually work day to day:
- the tools they use
- the shortcuts they rely on
- the habits that make their workflow click
It's the kind of hands-on exposure you can't get from a shared screen in a meeting. You pick it up by sitting next to someone, watching them work, and asking "wait, what's that tool for?"
A Client Relationship Built on Years of Trust
Being there also gave us a front-row seat to something we'd only understood abstractly before: the relationship between Procedure Technologies and Timely. It's built on years of consistency and trust, and on both sides caring about how things turn out, well beyond delivering what's asked.
Getting invited to Timely's retreat meant a lot to us. It showed how much the relationship has grown, and that both sides want to know each other as people, not just as names in an email thread.
Coming Home with More Than Souvenirs
We came back with notebooks full of ideas, a much deeper understanding of the product, and honestly, a lot of gratitude. Thank you to Procedure Technologies for believing this opportunity was worth investing in, and to Timely for welcoming us in like we belonged there, not like an outside contributor passing through.
This trip shifted our perspective, and we'll carry it into how we show up in this work from here.
If you want to see what working here looks like, have a look at our careers page.
Aashka Doshi and Kaushiki Krity
SDE2
Aashka Doshi has 4 years of experience building things that matter and taking ideas all the way to shipped features. She cares about clean, efficient code and pays attention to the small details so the larger system holds up as it scales. Kaushiki Krity has 2.5 years of experience and brings a product mindset to her engineering work. She likes building things that give people a meaningful experience, and occasionally wonders why something worked perfectly on localhost. Outside work, she's usually chasing a new adventure, hunting for good food, or convincing herself she needs another vacation.