Adding a draft of the case study for Drivvn (artwork still pending, client approval still pending) #10474
+72
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lient approval still pending)
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
joethreepwood
requested changes
Jan 27, 2025
| - Surveys | ||
| - Insights | ||
| - Web analytics | ||
| date: 2024-11-10 |
There was a problem hiding this comment.
This date is incorrect
| https://res.cloudinary.com/dmukukwp6/image/upload/posthog_octomind_bb047603a6.jpg | ||
| featuredCustomer: false | ||
| industries: | ||
| - 'Automotive, Agency,SaaS' |
There was a problem hiding this comment.
Suggested change
| - 'Automotive, Agency,SaaS' | |
| - 'Automotive, Agency, SaaS' |
Comment on lines
+4
to
+7
| logo: >- | ||
| https://res.cloudinary.com/dmukukwp6/image/upload/octomind_logo_673e0ed777.png | ||
| logoDark: >- | ||
| https://res.cloudinary.com/dmukukwp6/image/upload/octomind_logo_dark_a89deeee90.png |
|
|
||
| What if shopping for a new vehicle was a user-centered, seamless, thoughtful, online experience — no dealership required? | ||
|
|
||
| That’s the future Drivvn has been building. Supporting a network of more than 60+ automotive ecommerce providers, Drivvn is the digital engine behind global vehicle brands from Ford to Fiat. Known for creating brand experiences that are design-driven, human-first and still do great at the “selling” part — you’d almost think it was magic. |
There was a problem hiding this comment.
Suggested change
| That’s the future Drivvn has been building. Supporting a network of more than 60+ automotive ecommerce providers, Drivvn is the digital engine behind global vehicle brands from Ford to Fiat. Known for creating brand experiences that are design-driven, human-first and still do great at the “selling” part — you’d almost think it was magic. | |
| That’s the future [Drivvn](https://www.drivvn.com/) has been building. Supporting a network of more than 60+ automotive ecommerce providers, Drivvn is the digital engine behind global vehicle brands from Ford to Fiat. Known for creating brand experiences that are design-driven, human-first and still do great at the “selling” part — you’d almost think it was magic. |
|
|
||
| That’s the future Drivvn has been building. Supporting a network of more than 60+ automotive ecommerce providers, Drivvn is the digital engine behind global vehicle brands from Ford to Fiat. Known for creating brand experiences that are design-driven, human-first and still do great at the “selling” part — you’d almost think it was magic. | ||
|
|
||
| Under the hood, Drivvn’s Head of Product Engineering says it’s all PostHog. |
There was a problem hiding this comment.
Suggested change
| Under the hood, Drivvn’s Head of Product Engineering says it’s all PostHog. | |
| Under the hood, John Laramy, Drivvn’s Head of Product Engineering, says it’s all PostHog. |
|
|
||
| <BorderWrapper> | ||
| <Quote | ||
| imageSource="/images/customers/johny_laramy.jpg" |
There was a problem hiding this comment.
This image hasn't been added yet.
|
|
||
| With this birds-eye view, and the ability to run experiments and changes, John’s team can report to their own customers on how well their branded digital experiences are performing. Through dashboards, the reporting area helps them have those conversations — and it’s the data that is changing people’s minds. | ||
|
|
||
| “With one customer, I would say they were very against this [experimental, data-driven, A/B approach,” says John. “We then did one small-ish change — as subtle as changing the CTA on one page. When we showed the benefit of that, suddenly it was like a lightbulb moment. It clicked: ‘I understand the benefit of that now.’ After that, they were very keen to continue doing that approach.” |
There was a problem hiding this comment.
Suggested change
| “With one customer, I would say they were very against this [experimental, data-driven, A/B approach,” says John. “We then did one small-ish change — as subtle as changing the CTA on one page. When we showed the benefit of that, suddenly it was like a lightbulb moment. It clicked: ‘I understand the benefit of that now.’ After that, they were very keen to continue doing that approach.” | |
| “With one customer, I would say they were very against this experimental, data-driven, A/B approach,” says John. “We then did one small-ish change — as subtle as changing the CTA on one page. When we showed the benefit of that, suddenly it was like a lightbulb moment. It clicked: ‘I understand the benefit of that now.’ After that, they were very keen to continue doing that approach.” |
| /> | ||
| </BorderWrapper> | ||
|
|
||
| “One of the reasons we went with PostHog was because of the wide range of features,” says John. “We're using analytics heavily today across all those brand experiences. We're doing lots of feature flags, and also experiments…all towards helping people get to a clear outcome.” |
There was a problem hiding this comment.
Suggested change
| “One of the reasons we went with PostHog was because of the wide range of features,” says John. “We're using analytics heavily today across all those brand experiences. We're doing lots of feature flags, and also experiments…all towards helping people get to a clear outcome.” | |
| “One of the reasons we went with PostHog was because of the wide range of features,” says John. “We're using analytics heavily today across all those brand experiences. We're doing lots of feature flags, and also experiments - all towards helping people get to a clear outcome.” |
|
|
||
| “One of the reasons we went with PostHog was because of the wide range of features,” says John. “We're using analytics heavily today across all those brand experiences. We're doing lots of feature flags, and also experiments…all towards helping people get to a clear outcome.” | ||
|
|
||
| As someone who has been in engineering roles for more than a decade, John cares about the details. “We’ve used other tools like [MixPanel](https://posthog.com/blog/posthog-vs-mixpanel) and [Google Analytics](https://posthog.com/blog/posthog-vs-ga4), but I think the real thing that we were after was that it was third-party and cookieless.” |
There was a problem hiding this comment.
Suggested change
| As someone who has been in engineering roles for more than a decade, John cares about the details. “We’ve used other tools like [MixPanel](https://posthog.com/blog/posthog-vs-mixpanel) and [Google Analytics](https://posthog.com/blog/posthog-vs-ga4), but I think the real thing that we were after was that it was third-party and cookieless.” | |
| As someone who has been in engineering roles for more than a decade, John cares about the details. “We’ve used other tools like [Mixpanel](/blog/posthog-vs-mixpanel) and [Google Analytics](/blog/posthog-vs-ga4), but I think the real thing that we were after was that it was third-party and [cookieless](/tutorials/cookieless-tracking).” |
Internal links should be relative URLs
Comment on lines
+64
to
+72
| <BorderWrapper> | ||
| <Quote | ||
| imageSource="/images/customers/johny_laramy.jpg" | ||
| size="md" | ||
| name="John Laramy" | ||
| title="Head of Product Engineering, Drivvn" | ||
| quote={`“We’ve tried FullStory, MixPanel, Google Analytics and Plausible - but after building out prototypes, trying each tool, PostHog is where I want to be.”`} | ||
| /> | ||
| </BorderWrapper> |
There was a problem hiding this comment.
Suggested change
| <BorderWrapper> | |
| <Quote | |
| imageSource="/images/customers/johny_laramy.jpg" | |
| size="md" | |
| name="John Laramy" | |
| title="Head of Product Engineering, Drivvn" | |
| quote={`“We’ve tried FullStory, MixPanel, Google Analytics and Plausible - but after building out prototypes, trying each tool, PostHog is where I want to be.”`} | |
| /> | |
| </BorderWrapper> |
This is a duplicate
Yes, of course — that makes sense. I was under the impression you were asking me to do it this way (create the PR early and share with the user, despite not having artwork yet.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Closes #10341
Closes #10450
DO NOT MERGE
This is the first draft of the case study for Drivvn!
I've got a separate art request out with Lottie, and will now be sharing with the client for approval.
When I have the artwork, I will also organize formatting (internal linking, block-quote).
Add screenshots or screen recordings for visual / UI-focused changes.
Article checklist (to do after artwork and client review)