Chapter-by-Chapter Discussion Questions for The Go-Giver by Bob Burg: Chapter One - The Go-Getter

Like many MSPs, Rising Tide invests in our people through access to books, trainings, conferences, and certifications. At its core, this is not education for education’s sake: rather, we believe the best technical work starts with curiosity, and we consistently seek ways to foster curiosity as a skill. You see, we think the best solutions come not just from curiosity about technology, but curiosity about each other, about our clients, and about our community. We want to be known as people who ask better questions, understand others' perspectives with clarity, and are always hungry for more. We believe that personal growth will always drive technical and professional success for our team, and as a result, our clients.

Curiosity is not something you learn from an SOP, a certification, or a conference.

So how does a business foster curiosity? Curiosity is not something you learn from an SOP, a certification, or a conference. It’s something you develop by creating the time and space for yourself and your people to feel safe to speak up, to ideate, to build, and to iterate.

We are doing our best to build a culture of curiosity and progress in as many ways as possible, not just through structured education, but in choosing tools, conversations, and activities where we can intentionally seek to learn from and about each other and the world around us. The last part is very important at a core level: we believe every person brings a different background, toolkit, and perspective that strengthens and deepens our own, even — or especially! — when we disagree.

every person brings a different background, toolkit, and perspective that strengthens and deepens our own, even — or especially! — when we disagree.

As a fully remote team of 6, this can be pretty difficult to do since we can’t go out for lunch or have regular physical touchpoints other brick-and-mortar businesses may enjoy. So, one of the standard ways we cultivate this is through scheduled daily and weekly team conversations where we review customer issues, books or videos, conferences attended, or other interesting things we’ve seen that we want to share.

Most recently, we chose to essentially start a book club where we would read The Go-Giver by Bob Burg, together, and to invite clients and friends to review it with us on a weekly call. It was important to us that as a team expectation, we should make sure no one felt the demand too great on top of weekly work expectations. Thus, we decided on reading one chapter (7-10 pages) a week, to make sure that it felt accessible to everyone. (Reading ahead is absolutely allowed and encouraged, but we will only discuss one chapter a week!)

how do you allow for people to join in the conversation even if they didn’t get a chance to read?

The next question for a book club is: how do you facilitate conversation in a way that allows for people to share what was meaningful to them, or to join in the conversation even if they didn’t get a chance to read? In preparing for our book meetings, I sought out online resources with simple chapter-by-chapter discussion questions. However, as a very easy read, it seemed that most questions online covered concepts that spanned multiple chapters, which encouraged reading ahead and missing perhaps some smaller ideas worth savoring in each chapter.

Honestly, we figure we’re not alone in this desire to have simple questions and to walk carefully through conversations, so we've decided to share our own discussion questions, chapter-by-chapter! These questions are written without consideration for future chapters of the book and are meant to help bring in conversation about the topics and themes specifically covered in the given chapter. These questions are open-ended and if you’re facilitating, we encourage you to take the stance of no-wrong-answers, just as an impartial listener. You never know what perspectives or fresh ideas may come out of conversation.

Check out The Go-Getter Chapter One Discussion Questions here.

We’ll continue to add discussion questions and commentary on the book club as we move forward. Next things I’d like to try is to offer facilitation to a team member who has read ahead, to help them stretch their muscles of asking questions and building conversations. What other ideas should we tie in?

Join the Conversation

Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.

Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.

‍

About this Series

If you’ve already read Book Clubs, Conversations, and Curiosity, you know that at Rising Tide, we don’t host book clubs for the sake of reading. We use them as an excuse to talk, to listen, and to practice curiosity together.

The Go-Giver by Bob Burg and John David Mann is the first book that we've chosen to explore together in this way. Each week, we’re reading one short chapter together and using a few open-ended questions to spark real conversation: no lectures, no wrong answers, just reflection.

Below are our discussion prompts for Chapter One: “The Go-Getter.”‍

They’re written for teams like ours: busy, service-minded, sometimes too practical for their own good...who want to slow down long enough to notice what these stories have to teach.

How this guide is different from others you'll find online: We keep it chapter-focused. Every set of questions focuses only on the current chapter so there is no foreshadowing, no jumping ahead, no “we’ll get to that in Chapter 7.” The goal is to slow down and savor the smaller ideas that get lost when you rush to the big themes, and we're going to make sure that team members that are "behind" have enough data points to connect the dots and contribute even if they're not caught up to the current reading.

Use them however you like. Whether you’re reading along with us or just looking for a fresh team conversation starter, we hope these questions help you stretch a little, think differently, and see something new in yourself or your work.

Some Tips on how to use this Guide

1. Keep it simple. No slides. No structured lessons. Read a question aloud, give a solid 10-second pause, sometimes you have to let the awkwardness of silence drive the conversation.‍
2. Honor the one-chapter rule. No spoilers, no summaries! Stay inside the chapter or assigned reading. If someone raises a later theme, park it in a “Next Chapters” list and keep today focused. Similarly, don’t try to solve the book. Ask what this chapter made people notice or feel—nothing more.
3. Actively include people who didn’t read and make space for quieter voices. Use prompts like, “From this idea alone, what stands out?” Curiosity doesn’t require homework. Explicitly ask: “Anyone who hasn’t shared want to weigh in?” Intentionally invite two voices before anyone speaks twice‍
4. Time-box it. 15–30 minutes. One good discussion beats five rushed questions.‍
5. Close with a single takeaway. Each person names one sentence, idea, or action they’re taking into the week. Log it. Revisit next time.

If you tweak or add questions, tell us at partners@risingtidegroup.net. We’ll keep improving this tool for other MSP teams.

Chapter One Discussion Questions and Observations

Chapter One Questions

• How would you describe or define a go-getter?
• Is it a good or bad thing? Why?
• Do you consider yourself a go-getter?
• Do you know people like Joe, Gus, or Melanie? What do you think of them as people or colleagues?
• Why do you think the authors chose the name Pindar for the Chairman?
• What do you think Pindar's conditions are going to be?

Chapter One Observations from the Rising Tide Team

• Being a Go-Getter isn’t a bad thing!
• It’s important to remember that the authors of this book are likely flattening the depth of characters into caricatures to more cleanly get the point of their story across. This is important to remember because rarely in life will the humans you interact with be the fulfillment of the assumptions you make about them.
• Pindar is the name of a Greek poet who wrote odes of Victory. https://en.wikipedia.org/wiki/Pindar. Does this mean we can expect victory for Joe?
  

Creatures of a day! What is anyone?
What is anyone not? A dream of a shadow
Is our mortal being. But when there comes to men
A gleam of splendour given of heaven,
Then rests on them a light of glory
And blessed are their days. (Pythian 8)

Join the Conversation

Want to hang out in these conversations with the Rising Tide team? We meet Fridays at 9:30 AM ET to talk through important business, technological, and communal developments, and for the next 14ish weeks, The Go-Giver! If you’re an MSP owner, consultant, or service professional who wants to grow your team’s emotional intelligence alongside your technical skill, you’re welcome here.

Reach out to partners@risingtidegroup.net for the Rising Tide Fridays Teams link. Bring your coffee and curiosity: no prep required.

This release didn’t come with any headline grabbers—but for those deep in Halo, it delivered a handful of quality-of-life improvements and some thoughtful backend fixes. Below are the features worth your attention, especially if you're in billing, approvals, or building project automation.

Watch here now: https://youtube.com/live/WGnJXYeSxN4

Features Reviewed

Delegate Approvals for Tickets | v2.190 #830512 | 2:28
Ticket approvers can now assign delegates directly from the agent app ticket detail screen. Great for ITSM or structured orgs, but less relevant for fast-moving MSPs unless you're running approvals regularly.

Manual Proration Made Invoice-Ready | v2.190 #823611 | 4:18
A new checkbox on manual proration entries lets them show up in the invoicing screen immediately. Particularly useful for mid-cycle adjustments to annual billing, like licensing or domains.

Zero Draft Invoice Handling | v2.190 #819999 | 6:41
Halo will now ignore draft invoices created in Xero, preventing clutter and accidental syncing. You'll need to enable this in the Xero integration webhook settings.

Receive Stock Before PO Approval | v2.190 #829771 | 9:04
You can now receive items before a purchase order is approved. Risky for strict workflows but may fit fast-paced environments where hardware urgency overrides red tape.

Auto-Issue Items from Actions | v2.190 #837101 | 10:21
Set up actions to issue specific inventory items without user selection. Makes fixed-fee tickets more maintainable. Bug alert: doesn't yet work with quick actions—still requires a workaround.

Ticket ID in PDF Template Item Tables | v2.190 #837112 | 12:39
PDF templates can now pull the associated ticket ID into item tables—helpful for clarity in documentation, reporting, or client-facing PDFs.

Read-Only Appointment Subjects | v2.190 #829744 | 17:43
Admins can lock appointment subjects to match the ticket/project. It’s a small control that helps standardize records across large teams.

Editable Invoice Line Contract Links | v2.190 #823492 | 20:41
You can now edit the contract tied to a specific invoice line—especially valuable if you're tracking profitability across services with multiple contracts.

Prevent RMM from Changing Device Types | v2.190 #821917 | 24:58
ConnectWise RMM imports won't overwrite an existing device type anymore, assuming you check the new box.

QuickBooks Name Collision Workaround | v2.190 #829321 | 26:05
Halo now checks for matching item names before syncing, and links them rather than creating duplicates. A clever patch for a QuickBooks API issue.

Ticket Type as Rule Outcome | v2.190 #831422 | 27:28
You can now set ticket type via rule outcomes. Great for automating triage flows or conversions between types during lifecycle changes.

Team Custom Fields in Details Tab | v2.190 #831994 | 31:13
You can finally surface custom fields tied to teams directly in ticket details. Limited use cases for now, but it’s a step toward richer internal data visibility.

Granular Attachment Permissions | v2.190 #829812 | 32:36
Admins can now control who can view, edit, upload, and download attachments—down to the ticket type and role level.

Track Completion of Sales Lines | v2.190 #832113 | 33:58
Sales order lines can be manually or automatically marked as “Complete.” Adds helpful clarity, especially when you're tracking partial progress across installs or shipments.

Runbook Execution Modes (Parallel/Sequential) | v2.190 #830301 | 35:27
Control how runbooks trigger: run steps in parallel for speed or in series to avoid conflicts and ensure data accuracy.

Column Profiles for Invoices & Quotes | v2.190 #834755 | 44:01
Column profiles now work on sales orders, quotes, and invoices. You can personalize the data you see—and what you hide—for cleaner views.

Runbook Stats Tab | v2.190 #830996 | 35:27
Basic run metrics are now visible in a tab. Not yet robust for reporting, but a decent glance for usage and debugging.

For easier tracking, check out haloreleases.remmy.dev to filter and search HaloPSA updates by ID, version, and keyword. And join us on August 5th for a show with Robbie and Mendy: https://youtube.com/live/ApiYEmWJsPU! 

‍