VIP Welcome

Welcome to Your Onboarding Guide!

I’m excited to kick off our work together and want to make sure we start on the right foot. This guide will walk you through how I suggest setting up communications, account access, meeting cadences, and resource sharing to ensure a smooth collaboration. Think of it as a roadmap for working with me—one that we can always tweak as needed as we work together.

1. Communications

My Approach

I aim to sit as close to your team as makes sense. My goal is to be more than just an external contractor—I want to be a trusted resource and an integrated part of your team. I'm here not only for you, but for anyone I work with at your organization. I encourage open communication and hope your team feels comfortable reaching out with questions, ideas, or just to chat about what's on their mind.

Email

For most projects, I recommend adding me to your email ecosystem (e.g., robbie@clientname.com). This is especially helpful if you’re using Google Workspace or Microsoft Outlook, as it simplifies sharing dashboards, documents, and other resources within your organization.

  • Why add me? It streamlines permissions, making it easier for everyone to access shared materials.
  • Prefer external accounts? No problem! I’m happy to work with you using my LLC email (@curve.com) email if that’s what your IT team prefers.
⚖️
You might see Curve mentioned above and in other areas of my public life—but don’t worry, it’s still me! Curve is just the business name I use to organize my consulting work for tax purposes. Whether you know me as Curve or through a talent company, you’re always working 1:1 with me directly.

Slack

I’m flexible with Slack and can adapt based on how involved you want me to be.

  • Option 1: Add me directly to your Slack instance as a multi-channel guest.
  • Option 2: Invite me as a partner using Slack Connect (rob@curvemarketing.co)

Either way works, so just let me know your preference. Slack’s built-in flexibility makes communication quick and easy regardless of how we set things up.

Teams

If you’re a Microsoft Teams user, I recommend adding me to your Outlook ecosystem since Teams doesn’t support chatting with external folks as seamlessly as Slack.

  • Note: Because of the additional steps involved in accessing Teams, response times might be a bit longer (possibly up to a day or two). I’m happy to discuss any workarounds to speed this up!

2. Account Access

To hit the ground running, I’ll need access to some key analytics tools and data platforms. This is where sitting close to your team comes in—having the right access makes it easier for me to support you and your colleagues directly.

  • Analytics Platforms: Access to tools like Google Analytics, Adobe Analytics, or similar.
  • Tagging Solutions: If you use Google Tag Manager, Segment, or any other tagging platform, I’ll need access to those as well.
  • Data Warehouses: For direct data access, I’ll coordinate with your data team to set up read-only access to your SQL databases (MySQL, Redshift, Snowflake, etc.).

I’m happy to work with your IT team to address any VPN or security protocols needed.

3. Meeting Cadence

Regular check-ins are key to keeping things on track. Here’s what I recommend:

  • Weekly 1:1 meetings with you to discuss project updates, longer-term planning, and anything else that pops up.
  • Bi-Weekly 1:1s with other key stakeholders: This usually kicks in as we get deeper in an engagement, but have found it helpful to meet with dev, product, or other teams as well.
  • Ad-hoc communication: I’m always available for quick questions via Slack or other tools as needed.

Having regular touchpoints helps us stay connected and ensures I’m always aligned on your needs.

4. Knowledge and Resource Sharing

I’m big on documenting things so that knowledge is easily accessible to everyone. Here’s how I suggest setting up our shared resources:

  • Notion or Confluence: I use Notion for internal documentation, but I’m happy to work in Confluence if you already have it in place. I prefer these over Google Docs as they make it easier to update and find information, but happy to stick with Google Docs.
  • Existing Documentation: If you have existing documentation (Google Docs, JIRA notes, Confluence pages, or even SharePoint files), sharing those with me would be helpful. This could include things like data dictionaries or technical specs.

If you don’t have any documentation yet, no worries! I’ll work with you to create those resources during our engagement.

I want you to think of me as part of your extended team—always ready to help, share insights, and tackle any challenges that come up. This guide is just a starting point—think of it as my “ideal” setup. I’m flexible and more than happy to adapt to your preferred ways of working. Let me know if there are any other specifics you’d like to cover, and I’ll adjust accordingly.

Looking forward to a great collaboration!