Help Hackathon Ideas Grow By Exiting Properly

There is no easy way to describe this.

As a retrospective of coming out of the #BuildWithAI Hackathon, it's been a common theme about team formations and team ethics. Throughout the whole process and the inertia of what needs to happen at the event (and many like this one), that teams need to be formed. And there is a focus on how you get through this experience as a team and how do you collaborate, communicate and organise yourselves as a team. Some teams do it better than others.

Once teams have formed (and even before that), ideas and solutions are running fast to the end of the event. The keystrokes per second, the number of different design templates filled-in and meetings hosted is a mad rush of activity over a short period of time. There is a sigh of relief when the team submissions are in. Fantastic we made it. Great. High-5's all round.

Question. What is next? Does what you have, have a life of its own?

Something that I think some struggle with setting up team charters. Not just for the event itself but for exits from the event. This is not something that individuals are not normally needing to do. What happens after? Random people coming together to form teams are likely to separate and go their own ways. It is to be expected. Everyone comes into these events with their own goal. (It is lucky for some that have come in as a team beforehand). A few different questions and thoughts happen to what has been created collectively.

  1. What rights do I have to what I've built? What rights do others have to what I contributed?
  2. What if the idea and solution is worth driving into a next phase of its development? Who is in? Who is out?
  3. What if someone approaches me around that idea? Do I need to include others in the conversation?

There are many variations of these types of questions that pop up and after the hype of the event dies down, there is a sense of what next that needs to be consider.

I'm mindful that events where the random collisions of people to create something is a wonderful experience. We also need to acknowledge that this randomness also comes with the need to have some exit structure to make sure that we respect each other as part of this team.

I'm not an expert in this nor have I have the legal background in terms of Intellectual Property (IP). But I have seen how the lack of consensus or collaborative to exit out of these events can have destructive consequences and the great work of what has been achieved so quickly by this once team, suddenly doesn't have a life thereafter.

Putting the idea and solution that was produced in the centre of this discussion, I raise the hypotheses of:

How might we exit properly so to allow the idea to grow and prosper?
Brooke Berry

Scientist at Pathology Queensland

3 年

I'd love to see post hackathon support for teams to move forward. People may come to these due to existing blockers and barriers in their organisations and communities, so how do the huge strides translate to life back in the grind? Often the greatest barriers to innovation are culture, politics and bureaucracy, which are a different skillset.

Lyn W.

Marketing Leader | Collaborator | Social Influencer | Enterprise Technology | Integrated Marketing | Channel Enablement

3 年

Is it a sign of a good Hackathon that this discussion even takes place ?

Himanshu Joshi -.

AI Strategy & Implementation | Revenue Optimization | Digital Transformation | Start-up Operations Excellence

3 年

Jason Lowe Very well brought out ! Thanks for posting

要查看或添加评论,请登录

Jason Lowe的更多文章

  • The Purposeful Question "Are We Done Yet?"

    The Purposeful Question "Are We Done Yet?"

    Yesterday, I wrote this article Validations vs Solutions - Same But Different where I referenced a few different…

  • Validations vs Solutions - Same But Different

    Validations vs Solutions - Same But Different

    Back in 2020, I wrote this article Data Driven Design, where I focused upon the model of thinking about business…

    2 条评论
  • Let's Talk Lean Not Cost (backed by data)

    Let's Talk Lean Not Cost (backed by data)

    (It feels weird that this is a first article in a VERY long time that it feels like a new chapter. It also feels like…

  • #ThankYou For The Opportunities

    #ThankYou For The Opportunities

    ..

    26 条评论
  • BIG BANG change is HARD (but) ...

    BIG BANG change is HARD (but) ...

    There's been a BIG BANG change recently. And it's actually changed a few different perspectives around it.

    6 条评论
  • Inspired by Data Driven Design

    Inspired by Data Driven Design

    The title was inspired by a few different things. The ever-present data-driven businesses.

    22 条评论
  • (Open != Free) && (Buy || Invest)

    (Open != Free) && (Buy || Invest)

    The heading is cryptic and there is a purpose because it is a complex system. There are two things that has been going…

  • Did #BuildWithAI but not finished.

    Did #BuildWithAI but not finished.

    Good morning everyone. (And just reading that it felt like a roll-call).

    26 条评论
  • Influences — Energy … This Is Why …

    Influences — Energy … This Is Why …

    (Update) Morning everyone - this is the last article in this influence series that I've documented stuff around how I…

    3 条评论
  • Influences — Technology

    Influences — Technology

    (Update) It's a natural occurrence that technology would be an influence. Ever since reading through an IBM catalogue…

社区洞察

其他会员也浏览了