Kirstie Whitaker
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
--- breaks: False --- # Emergence as _The Turing Way's_ Strategy _The Turing Way_ is a living book. It is written by a community, who are themselves human, ever changing, beautiful and creative. What they can - we will - create is better than anything any one person could imagine. In this section of the book, the founder of _The Turing Way_, Kirstie Whitaker, talks us through the principles of [Emergent Strategy](https://fortelabs.co/blog/emergent-strategy-organizing-for-social-justice/) and how they direct and inform her leadership of the project and of the [Tools, Practices and Systems Programme](https://www.turing.ac.uk/research/research-programmes/tools-practices-and-systems) at [The Alan Turing Institute](https://www.turing.ac.uk/about-us) more broadly. You can read [the book](https://www.akpress.org/emergentstrategy.html) by [adrienne maree brown](https://adriennemareebrown.net) from many different sources. This [blog post by Forte Labs](https://fortelabs.co/blog/emergent-strategy-organizing-for-social-justice) is a great overview too. Brown uses Obolensky's definition of _emergence_ as "the way complex systems and patterns arise out of a multiplicity of relatively simple interactions". The following section of the chapter digs into each principle in turn. They aren't really separable, and are lenses on the whole philosophy that brown espouses. As she says in the introduction to the book: > You can read the book with others, assess each other and assess the groups and circles you move in. > Come up with new words and new observations for all of this, notice how it connects and echoes other theoretical frameworks. > Underline everything that moves you and then give it to someone younger than you. > Come up with workshops and retreats around this work. > Take it, run, go, grow, innovate, emerge. That's what Kirstie did with _The Turing Way_, and what she hopes to inspire across the TPS Programme at the Turing. Remember that you can make adjustments to this text yourself as your understanding evolves. In fact, she - we - hope that you do. Thank you for being here. The principles of emergent strategy: * [Small is good, small is all (The large is a reflection of the small)](#small-is-good--small-is-all--the-large-is-a-reflection-of-the-small-) * [Change is constant (Be like water)](#change-is-constant--be-like-water-) * [There is always enough time for the right work. There is a conversation in the room that only these people at this moment can have. Find it.](#there-is-always-enough-time-for-the-right-work-there-is-a-conversation-in-the-room-that-only-these-people-at-this-moment-can-have-find-it) * [Never a failure, always a lesson](#never-a-failure--always-a-lesson) * [Trust the People (If you trust the people, they become trustworthy)](#trust-the-people--if-you-trust-the-people--they-become-trustworthy-) * [Move at the speed of trust](#move-at-the-speed-of-trust) * [Focus on critical connections more than critical mass—build the resilience by building the relationships](#focus-on-critical-connections-more-than-critical-mass-build-the-resilience-by-building-the-relationships) * [Less prep, more presence](#less-prep--more-presence) * [What you pay attention to grows](#what-you-pay-attention-to-grows) ## Small is good, small is all (The large is a reflection of the small) Everyone who works within Tools, Practices and Systems (TPS) at the Turing should have a grand vision for a change that they want to see in the world. Maybe it's making all research reproducible at the time of publication. Maybe it's ensuring that every data set comes with documented metadata and provenance (a data paper for example). Maybe it's investing in community-created open source software to improve research efficiency. I want to very, very deeply support and encourage those big dreams. They can seem intimidating, impossible, too much for one person / project / community. Sometimes it can be tempting to want to lie down on the floor and give up when you realise just how stacked against those collaborative practices our current incentive structures can be. What I love about this first principle of emergent strategy is that it gives us a pathway to making that change. * Want to see a kinder world? Be kind to the next person you interact with. * Want to see a more reproducible publishing ecosystem? Help the next person you collaborate with to re-run their analyses to confirm the same answer. * Want data scientists to be more representative of our global community in terms of ethnicity, gender, sexuality, disability and so many more dimensions and their intersections? Encourage the next person you mentor to share their perspective. Especially if that person is yourself :sparkling_heart: ## Change is constant (Be like water) It's exciting to work in a field like data science where the boundaries of what is known and what can be known is changing every day. It can also make finishing a task incredibly difficult! The goal posts move on a weekly or monthly basis. Every new research paper that you read can change your perspective and potentially adjust the trajectory of your work. _The Turing Way_ is designed to be ever evolving. We embrace a version controlled workflow, so you can't really break anything too badly, and we keep a history of where we have been. A contribution - any contribution - is a step in the right direction. Try not to over think the completeness of your work. As with a stream, a river, or the ocean, there will be more contributors to take the project forwards. Whatever you can do right now, in this moment, is what we need and what we appreciate. ## There is always enough time for the right work. There is a conversation in the room that only these people at this moment can have. Find it. One of the things that I've heard clearly in the first few years of creating _The Turing Way_ is how uncomfortable people feel in agenda-less spaces. I ran open [coffee chats](https://twitter.com/kirstie_j/status/1239455513080926208) every workday morning from the first UK COVID lockdown in March 2020 to Easter 2022 when I started my maternity leave. I LOVE the creativity and inspiration that comes from completely open ended conversations. I had to listen, get to know some of the regulars, sense what they were interested in talking about that particular day, and then ask the right questions to allow the conversation to evolve. There's always a bit of trial and error involved, and so part of finding the conversation for _these_ people in _this_ room is balancing listening and experimenting. For me, this is core to the concept of emergence and community-led creation. If someone else is making the agenda and dictating the direction, we miss so much of the creativity that could come from these particular people and their lived experiences. Beyond the literal example of finding a conversation for this group of people, lies the broader principle: there is always enough time for the right work. * Sometimes that means being careful and thoughtful about creating agendas for meetings. * Sometimes it means saying no to urgent work to prioritise the important tasks. Infrastructure work, and open, collaborative effort, has always tended to fall down an individual's or an organisation's priority list. But if we don't start doing that work today, it will never be started, and then we'll never achieve transformational change. * Sometimes it means channelling the fact that _the large is a reflection of the small_. Does that person need a little extra time to be heard and understood today? Maybe that _is_ the work that you're supposed to be undertaking today. Deadlines be damned. ## Never a failure, always a lesson Bugs are features. The typos - or broken links - in _The Turing Way_ are invitations for new contributors to get involved. Together, we are trying to change the world. Change research culture, make data more accessible, democratise access to knowledge, and ensure that artificial intelligence is harnessed for a public, global good. We need to dismantle our own biases - sexism, racism, ableism, colonialism, capitalism - in order to reach this potential. We will all fail in this endeavour, every day. The goal is to get up and try to improve - incrementally - every step we take. Be vulnerable, be brave, and be gracious in recognising the learnings of others as they stretch beyond their comfort zone. (If you'd like to read more about courage and vulnerability in leadership, I recommend [Brene Brown's](https://brenebrown.com/) book [_Dare To Lead_](https://daretolead.brenebrown.com/). In particular her exercise on [operationalising values](https://brenebrown.com/operationalizing-your-orgs-values/) is really fascinating. It's so easy to _say_ the right thing. What takes conviction and resilience is making the changes to identify and then actually _do_ the right thing.) ## Trust the People (If you trust the people, they become trustworthy) This principle is inspired by the writings of [Lao Tzu](https://en.wikipedia.org/wiki/Laozi), an ancient Chinese scholar who is reputed to have written the [_Tao Te Ching_](https://en.wikipedia.org/wiki/Tao_Te_Ching). > "When the Master governs, the people > are hardly aware that he exists. > Next best is a leader who is loved. > Next, one who is feared. > The worst is one who is despised. > > If you don't trust people, > you make them untrustworthy. > > The Master doesn't talk, he acts. > When his work is done, > the people say, 'Amazing: > we did it, all by ourselves!'" It can be tempting to control a situation (or at least try to feel a sense of control). And - as a corollary - it can be tempting to try to control the people you're working with. I certainly can fall prey to advocating so strongly for a direction that I believe in that I come across as directing - telling - team members what to do. But, as Lao Tzu knew 2500 years ago, the very best work comes from the people who are trusted and who have the safety and the space to find their motivation and alignment with the project goals. ## Move at the speed of trust No one ever felt an increase in trust when given a deadline or time constraint to get there. Building and nurturing trust requires time, patience, and a little deftness to take advantage of opportunities when they arise. We have project goals for _The Turing Way_ and we have to report on the effort we have made to our funders. It can be hard not to be driven by deadlines. But it is imperative that we build as much space as we possibly can to move at the speed of trust. The journey is so much more important than the destination. Especially if that destination can't be reached by this particular team at this particular time. _Change is constant._ _Be like water._ ## Focus on critical connections more than critical mass—build the resilience by building the relationships One of the other temptations that we are incentivised towards is to count things. Number of chapters, number of contributors, number of workshops, amounts of funding, how many projects we have inspired. We have to report these to our funders in order to keep the lights on, but I encourage you to focus more on the critical connections - those interpersonal dynamics that allow you to build trust, and manifest the change that you want to see in the world on an individual level before you try to scale it. We can do both. We can increase our impact, include more people, welcome their contributions and support the pathways along which their careers develop... but not if we are too narrow in our definitions of success. We will make a deeper and more profound change in the world by telling the stories of the individuals who make up our community in their own words and in ways that allow others to build their own confidence and trust. ## Less prep, more presence For me, this principle is very similar to _there is always time for the right work_. Finding the emergent discussion. Identifying the gaps, and individual contributor's strengths and motivations. Building a deep trust and alignment in the purpose and cultural changes that _The Turing Way_ can manifest. We can think carefully about how to build spaces to develop those conversations, but we can't control the direction of the discussion, and we can't force creativity or collaboration. * We can control our own behaviour. * We can be present. * We can reflect. * We can respond - ideally with kindness and compassion. * We can be ready to act when the opportunities emerge. ## What you pay attention to grows Everything and everyone requires time and attention. We have illustrations capturing garden analogies throughout _The Turing Way_. That's because we care deeply about nurturing and sustaining our community. We want our members - and our project - to thrive. Where we place our focus, our energy, our kindness, and our trust, will grow.

Import from clipboard

Paste your webpage below. It will be converted to Markdown.

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully