Skip to main content

Winging it — People who master it make you believe that they are following its definition

What does “winging it” mean? We all have done it, but do we master it?
Definition:
To wing it is an idiom that means to improvise, to do something without proper preparation or time to rehearse. People often talk about winging it when they have to do something difficult that they didn’t have time to prepare — like a make speech or give a presentation.
Those who are regularly successful in it are actually memorizing their speeches and the facts from the speech. They practice and practice. Then when the actual meeting or speech or presentation comes, they have the confidence because in the worst case, you memorized everything and you can go by the script. With that confidence, you find opportunities during your presentation to be more natural and that natural behavior keeps your audience engaged; some may say that you are winging it and that you are very good in it but I call it “being very prepared”.
Don’t think that this only applies to your senior management team. This applies to everybody in your organization whether you are in a meeting with 3, 5, 10 or more people.
Try it in your next meeting. Carefully read the agenda for the meeting and come very prepared. Then when you are in this meeting, keep your laptop, notebook and your smartphone away and pay attention to all the discussions. You will be very natural and your points will come across much stronger.
Conclusion:
Those who you perceive as great in winging it, they actually rehearse and go against the definition of “winging it”.
Thank you for reading this article. Please follow me here or you can also find my articles at http://www.almirsCorner.com
Almir Mustafic



Labels:

Comments

Post a Comment

Popular posts from this blog

Daylight saving time and A Software Engineering state of mind ?

You may be wondering what the Daylight saving time has to do with a software engineering state of mind. When thinking about writing this article, at first I thought to start with the following joke and I am: “ Did you know that the Daylight saving time was started because a software developer coded a function that does smart timezone and configurable calculations and then this developer created a problem to solve to use the algorithm; hence, the Daylight saving time was born. ” This is a joke, but  on a more serious note , this brings me to a state of mind in software engineering that make this joke a reality to some degree. How many times did we find ourselves in situations where we learned something new in programming and we looked for ways to apply it at any cost? How many times did we see a cool new feature from a creator of a framework and we decided to use it even though that was not the right solution for the problem or maybe there was no problem to solve in the ...
Post a Comment
Read more

Leaders/Mentors in my life

I have been blessed in my software engineering career with great leaders. Some of them challenged me in technical skills. Some of them challenged me in my organization and leadership skills. Some of them challenged me in both. And all of them made me a better software engineer, a better senior engineer, a better solutions architect, a better teammate, and a better leader. If you are a student, find yourself a mentor. If you are a junior software engineer, find yourself a mentor. If you are an experienced software engineer, find yourself a mentor. Remember, you write your own definition of success and you are your own critic. That may mean that you TRY to perfect every stage of your career, or that may mean that you skip some stages in your career. Remember, you are in control. That’s all I wanted to say today :) Keep geeking out. Almir
Post a Comment
Read more

OWNING your sandbox

OWNING your sandbox. As software engineers we all like to work on latest technology and coding new applications. People generally don’t like spending a lot of time maintaining the code. However, in the world of microservices the owners of each microservice are very well known and defined unlike in the world of monolithic applications. That means that you own it in the true sense. You own the code. You own the QA environment. You own the Stage environment. You own the production environment and all the errors that come along with it :) On positive note, you have a lot to be proud of and you can turn it into opportunities :) You own something that is contributing your company’s customers and what you do responsibly affects the lives of many people in a positive way. Almir Mustafic
Post a Comment
Read more