Three Topics at a Time: A Study Group’s Road to Certification

Three Topics at a Time: A Study Group’s Road to Certification

The following account is a made-up story about an imaginary study group, the kind of team that forms around a certification goal. It shows what happens when learners cap the number of topics they have open and finish each one before starting the next. The names are invented, the numbers are round, and the lessons are the part to keep.

The group and its goal

Four colleagues at a mid-sized logistics company, Farah, Dev, Lucia and Tomasz, decided to prepare together for a cloud and delivery certification, with an exam date set twelve weeks out. Farah worked in support, Dev in testing, Lucia in infrastructure and Tomasz in development. They agreed to meet twice a week and study on their own in between. Their enthusiasm was real, and so was their problem: the syllabus was enormous, and each of them had collected a stack of resources.

Weeks one to four: everything open

The early plan sounded sensible. Each person would dip into several topics each week to stay broad: container basics, pipeline design, monitoring, infrastructure as code and a little scripting. The group maintained a shared sheet listing topics, and by week four it showed nineteen topics marked “started”. Only two were marked “done”, and both had been easy.

The weekly meetings began to feel awkward. Farah would explain half a concept she had touched on three weeks earlier, forget a key step and apologise. Dev found that revision notes for four different topics all ended in the same place: a bullet reading “come back to this”. Lucia realised she had watched more than thirty hours of video and could not summarise any single module without looking at the screen. Nobody was lazy. They were simply spread thin, a pattern familiar from the article on the usual blind spots learners carry into DevOps work and ways to close them, where gaps often appear because topics were sampled and not completed.

The turning point

At the week-five meeting Tomasz brought a printout of the shared sheet and drew a line under the first three started topics. “What if only these are allowed to be open?” he asked. Everything else, he proposed, would sit in a “later” column until one of the three was finished. The group argued for ten minutes. Dev worried about falling behind on breadth. Lucia pointed out that they were already behind on depth, and that an exam tests whether you can apply a topic, not whether you have heard of it.

They adopted the limit of three open topics for the group, and each member would have at most two personally. Finishing meant a specific thing: being able to explain the topic aloud in five minutes and complete a small practical exercise without notes.

Weeks five to eight: the effect

Containers closed first, in nine days. Pipeline design took twelve. Scripting, which had lingered for a month, finished in a week once it had the group’s undivided attention. The “done” count rose from two to eight within four weeks. More importantly, the quality of the weekly meetings changed. Instead of apologising, people taught. Each finished topic left behind a one-page summary written by the person who knew it best.

The limit also exposed a hidden bottleneck. Monitoring stayed open far longer than expected, and it blocked a slot every week. Rather than starting something new to avoid it, the group paired up on it, which led to a cleaner explanation and a lab environment everyone could reuse. Without the ceiling, the topic would probably have been postponed indefinitely, and the same unfinished feeling would have followed them into the exam room.

A side note on information overload

The group also noticed how much reading they did that never connected to the syllabus. One member had been browsing a wellness-themed site, AskDoctorLive, which pairs a discussion forum and articles with hospital and doctor listings, during breaks, and admitted that a quick look often stretched into half an hour. They agreed that break-time reading was fine, but that it would never count as study and never take a slot.

Weeks nine to twelve: the final stretch

With the remaining topics, the group kept its habit of finishing before beginning. They built a short revision loop: each week they returned to one finished topic, explained it again and fixed any weak spot. Practice questions were attempted only on topics already closed. By week eleven, the sheet showed sixteen topics done, two open and one deferred. The deferred topic, they decided, was lightly weighted in the syllabus and could be skimmed on the last weekend.

Their approach to practical reasoning echoed the lessons in this piece on building critical thinking for DevOps problems: clear thinking comes from working one problem through to its conclusion, not from touching many problems briefly.

The outcome

On exam day, the four colleagues felt calmer than they had expected. Three passed on their first attempt. The fourth, Dev, missed the mark by a small margin and rebooked after a short targeted review of the one area that had been skimmed. He later said that the group’s habit, rather than the certificate, was what stayed with him: when he returned to his testing job, he set a limit of two open test plans and noticed the difference within a fortnight.

What the story illustrates

  • Counting open topics honestly reveals how thin the effort has been spread.
  • A small group limit, backed by a clear definition of “finished”, turns study into steady progress.
  • Bottlenecks become visible, because a stubborn topic keeps occupying a slot.
  • Finished topics leave artefacts, such as summaries, that the whole group can reuse.
  • The habit transfers to the workplace long after the exam is over.

For any learning group or individual, the sequence is simple to copy. List what is open, set a ceiling, define finished in concrete terms, and finish before you pull the next topic. The syllabus will still be large, but it will shrink one completed item at a time.