Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a blog post to offer messaging about the category in which to place Kedro #1

Closed
2 of 4 tasks
NeroOkwa opened this issue Dec 5, 2022 · 6 comments
Closed
2 of 4 tasks
Labels
Blog post creation Blog posts (ideas and execution)

Comments

@NeroOkwa
Copy link

NeroOkwa commented Dec 5, 2022

What is this?

It is common to see misconceptions around which category Kedro should fall into across blog posts, data science articles, and industry rankings.

These misconceptions include Kedro being seen as an orchestrator, or platform like SageMaker, or in a general category like ML or AI. Such as in here, and here

The goal is to define the right category for Kedro (e.g. development framework), and position Kedro there, starting with a blog post.

Why do we care about this?

This wrong perception determines if and how users implement Kedro for their projects.

Secondly, during client projects, if they think Kedro is a platform, they would be reluctant to use it because of the fear of ‘vendor lock-in’, or if they are already locked-in with another vendor.

Effectively communicating our unique positioning and category, would drive adoption of Kedro.

What needs to happen?

  • Benchmark our current perceived position
  • Define our category
  • Write a blog post about this
  • Approach industry map makers, and communicate kedro's category
@NeroOkwa NeroOkwa changed the title Messaging - Creating a Kedro Category Messaging - Create a Kedro Category Dec 6, 2022
@NeroOkwa NeroOkwa changed the title Messaging - Create a Kedro Category Messaging - Define a Kedro Category Dec 6, 2022
@stichbury
Copy link
Contributor

You've seen this landscape from LF? https://landscape.lfai.foundation

It's really neat and it's open source (and the CSV is available for the data behind it). We are in the Workflow category within it. Are we OK with that?

I do think we can build upon it to write a blog post to communicate it.

I don't know that we need to put in too much extra effort to define a category for ourselves if we have this already? I'm tempted to say we should omit the first 2 of your tasks and concentrate on the latter two.

image

@NeroOkwa
Copy link
Author

@stichbury I have had a look, and I agree. We can build on this category through the blog post.

@NeroOkwa NeroOkwa transferred this issue from kedro-org/kedro Jan 31, 2023
@stichbury stichbury changed the title Messaging - Define a Kedro Category Create a blog post to offer messaging about the category in which to place Kedro Jan 31, 2023
@stichbury stichbury added the Blog post creation Blog posts (ideas and execution) label Jan 31, 2023
@stichbury
Copy link
Contributor

Do you still want this @NeroOkwa and, if so, are you able to create it?

@astrojuanlu
Copy link
Member

I think it would be a nice companion to the research @NeroOkwa has been doing on competitors 👍🏽

@NeroOkwa
Copy link
Author

NeroOkwa commented Jan 15, 2024

@stichbury yes I would like to still do this.
@astrojuanlu Let's do this together to also include your research on kedro framework.

@astrojuanlu
Copy link
Member

It is common to see misconceptions around which category Kedro should fall into across blog posts, data science articles, and industry rankings.

These misconceptions include Kedro being seen as an orchestrator, or platform like SageMaker, or in a general category like ML or AI. Such as in here, and here

This is indeed an issue.

However it's clear that we won't solve this with one more blog post, or adding more FAQs or callouts.

Let's keep focusing on kedro-org/kedro#3012

@astrojuanlu astrojuanlu closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blog post creation Blog posts (ideas and execution)
Projects
None yet
Development

No branches or pull requests

3 participants