Her first job. Second week. On Friday, her lead had casually mentioned she could start running the weekly bug-triage meeting. Wednesdays, fifteen minutes, three or four people. It sounded like a small thing, and that made it worse: when you fail at something small that everyone else seems to handle effortlessly, it stands out even more.
The weekend started with a feeling she needed to prepare, but didn't know for what. She'd never run a meeting before, let alone one with colleagues who all had years more experience than her. The thought of opening with “Hey, so, which bugs do we have?” and then watching someone else take over was unbearable. At the same time, there was this ambition to do it well enough that everyone walked away thinking: that was good.
On Saturday evening she typed into her chat: “How do I facilitate a short technical meeting when I'm the youngest person in the room?” The response was long, full of tips about conversation techniques and facilitation strategies that all assumed more confidence than she currently had. Further down, almost as an afterthought, one suggestion stood out from the rest. Everyone enters their points independently before the meeting, then the team votes together on where to start. The link led to Grounds-Up.coffee.
The friend who'd already found it
On Sunday afternoon she told a friend about it, someone who'd been in a similar role for a few months. He laughed and said he'd been using that exact thing for his sprint retros for weeks now. He'd stumbled onto it the same way she had, out of a similar frustration, because his retros kept feeling the same.
What he told her sounded encouraging. People enter their points beforehand, often between two other tasks, in a quiet minute. By the time the meeting starts, everything's already on the table. No awkward silence at the beginning, no moment where he has to ask if anyone has something. The hardest part was sending the link and trusting that people would actually fill it in. The first time, two out of five hadn't entered anything beforehand. By the third time, everyone had.
That was exactly the reassurance she needed. Someone in her situation, no facilitation pro, no manager, had been using the tool for weeks and it had made the whole thing easier for him. She asked how long the setup had taken. He said: “Five minutes, maybe less.”
Sunday evening
She set up a room for herself, just to see what it felt like. She typed in three questions she imagined for Wednesday: “Which bug is blocking you the most right now?”, “Is there anything that's been sitting untouched since last week?”, “Have you noticed something that doesn't have a ticket yet?” She entered a test item herself, voted on it, watched it appear on the list. The whole thing took less than five minutes.
What calmed her down was how simple it was. No complicated setup, no training she'd have to explain to her colleagues. Just a link and three questions. If it didn't work on Wednesday, nothing bad would happen. She'd just run the meeting the old way and try something different next time. That low risk was what made the attempt feel possible. A Wednesday that would have stayed inconsequential even if nothing had changed.
The real thing
On Tuesday morning she sent the link to the three colleagues, along with a short message: “Hey, I've set something up for tomorrow and would love for you to add your open bugs here. That way we can prioritize together right away.” No big announcement, no explanation of what Grounds Up was or why she was changing the format.
Wednesday morning, ten minutes before the meeting, she checked the room. All three had entered their points. One colleague who'd barely ever spoken up in team meetings had written two items, one of them the exact thing she'd mentioned in passing by the coffee machine the week before. Both items got votes from the others. Both got discussed.
It felt like a small, private win. She messaged her friend: “It worked. Everyone had entered stuff beforehand.” He replied with a thumbs up and “Told you so.” That was all she needed in that moment.
She hadn't said anything, hadn't told anyone what to do, hadn't explained how meetings should work better. The format had done the work, and all she'd invested was a Sunday evening with five minutes of setup and a link on Tuesday. The reason the quiet colleague suddenly had two relevant items on the list was that the format made contributing a prerequisite, before anyone opened their mouth. Nobody had to find the courage to speak up. The floor belonged to everyone from the start.
What happened after
In the following weeks, the quiet colleague entered items regularly, as naturally as everyone else. Nobody had to encourage her.
When the tech lead joined one Wednesday because an urgent bug affected everyone, he saw the items on the list and asked afterward why the weekly never ran like that. A few weeks later, the Monday sync adopted the same sequence for the first time: collect topics, then vote, then talk. When someone asked where the idea came from, the tech lead pointed at her spot in the call.
She hadn't proposed a culture change and hadn't needed to convince anyone. A Sunday evening, five minutes, and a link had been enough to make visible who on the team had something to contribute all along, once the format allowed it. The only person she'd asked for advice was a friend who'd been in the exact same spot.
Which of your meetings would you like to try it with?