Give people space
As an Engineering Manager at Grab, I recently engaged in a coaching session to enhance my feedback skills during the 360 season conversation. Despite my initial belief that I had mastered the art of management after three years, I approached the session with an open mind and was pleasantly surprised by the valuable insights gained.
Two key takeaways continue to resonate with me a week later: the importance of cultivating curiosity and allowing space for growth. These concepts have significantly influenced my approach to providing feedback, adding a fresh perspective to my managerial toolkit. Stay tuned as I delve into these transformative ideas in my latest blog article!
1/ Be Curious
Historically, my 1:1 conversations went like this:
me: Hi, I noticed there was an issue in ___. can you tell me more about that? them: don’t worry I fixed it. me: thanks for fixing it. but how can we prevent this from happening again? them: I will do better next time. me: thats not the answer I was looking for. can you be more specific? them: I will be more careful. me: … me: let me just give you the answer. What if we try doing A, B, and C?
In retrospect, I acknowledge the limitations of my approach as I lacked sufficient information to confidently recommend A, B, and C. I now recognize the importance of cultivating curiosity about the problem at hand before imposing my own biases and assumptions. Moving forward, I aim to adopt a more inquisitive mindset to better understand and address challenges.
2/ Give them space to solve their own problems
In problem-solving, guiding individuals with strategic questions proves more effective than managers simply offering personal advice. By delving into the root cause through thoughtful inquiry, people can tap into their creativity to discover solutions on their own. This approach fosters self-discovery and empowers individuals to navigate challenges autonomously.
More posts
Posts
Give people space
From Snowy Tomato Slices to Tea Debates: Navigating Ukrainian Culture
Navigating Cultural Differences: Hilarious Translation Fails.
Writing Style for Slack
Batch Prompting (cost reduction for LLMs/ChatGPT)
NSFW Image detection on Digital Ocean Apps
Top 5 Junior tech roles to become software engineers
Top Ruby exploits in rubygems.org
Life Design: Daily Actions
Designing a distributed web crawler
System Design Interview Format - 6 Steps to passing
SSO / SAML to JWT: A system design problem
How and when to add foreign key constraints
Fraud Detection with Ruby on Rails
Rails: No downtime data migrations
Letter Avatars with Serverless
Wildcard Google Auth for multiple subdomains
I graduated from a code school. Now what?
Bulk email sending with Ruby
Rails tip: Returning
Rails tips: Fast Relation Detection
Regex: Escaping Slashes
Limited Retry Pattern
Adding Queues to your models
Hosting Side Projects for Free
Adding search to Atlanta Startup Jobs
Rails Patterns: Builders and Models
Ruby on Rails Grape gem: Pros and Cons
Otto meet Retrofit: How to build a scalable and performant Android application
Atlanta Startup Jobs - Scratch your own itch
SideProject: HappyBeam - Meditate and improve
How to win a hackathon
One Rails App Two Web Applications
Angularjs Rails and SEO Part 2
Angularjs Rails and SEO Part 1
Buying my first real estate investment
How to get OSX git branch name in console
How to start web consulting
Goodie Hack #2
What it takes to be entry level Rails developers
Rails 4.1 enums: How not to handle states
My path to success
Twitter bot on Heroku
Rails and Redis URL Shortener in same application
Tagging Models
Gem Configuration Defaults
Custom Environments with Rails 4
NodeJS Chat Guide
Rapid Ticket Purchasing and the extendable web
Extending Active Record in Rails 4.1
Reporting with Rails Part 2
Reporting with Rails Part 1
Setting up a Ruby on Rails 4.0.1beta1 with OSX Mavericks 10.9
subscribe via RSS