Archive for the Category Conferences

 
 

ACS Conference: Preparing for a leadership role

Report on ACS Young IT conference in Adelaide - Day 1, 30th May

Preparing For a Leadership Role by Stephen Kowal

A definition: Motivating (inspiring) a person or people to achieve a goal, while helping those people achieve their goals.

Every position is a leadership position, but not every person is a leader. You can choose whether to lead within your role.

Understand your values and other people’s values, then you’ll know what is needed to inspire yourself and them.

Your performance, not your role is what determines your success. Do whatever you’re doing now with passion, even if you don’t like it.

Luck doesn’t exist - instead, there are always causes for something happening.

Questions: Stephen gave $50 (!) to the person who asked the first question, but only $2 to the person who asked the second question, because “being second isn’t nearly as valuable as being first”.

ACS Conference: Leadership

Report on ACS Young IT conference in Adelaide - Day 2, 30th May

Leadership by Linda Zeelie

A definition of leadership - “the lifting of people’s vision to a higher sight, the raising of their performance to a higher standard, the building of their personality beyond its normal limitations”

There are poor, good and great leaders. Are you working for a great, or at least a good leader? If you are, you’ll be extended and your performance will improve. If not, you’ll become doubtful of your abilities and you’ll become less capable over time.

To become a great leader, learn from other leaders (good and bad). Working with a bad leader is useful to learn about leadership, but it’s not good for you. So learn your lessons quick then get out!

Have a vision AND a plan. You should be able to record and explain it simply and concisely. If you can’t explain it simply, you simply don’t know it.

No decision is always a poor decision. Make a decision, and once you’ve made it, be very, very decisive. Do not waver, own the decision!

When things go well, share the success. When things go wrong, own the failure. Take responsibility, even when it’s not directly your fault.

Linda had a very strong conviction to her speaking. I could sense that she felt that what she was talking about was really important, and many of her points stuck with me. Definitely one of the best talks of the conference.

ACS Conference: The Art of Visual Effects

Photo credit: broewert on Flickr

Report on ACS Young IT conference in Adelaide - Day 1, 29th May

The Art of Visual Effects by Didier Elzinga, CEO of Rising Sun Pictures

What follows are my summaries of the main points I took away from this talk.

At first, hard work (long hours, late nights) is important. But at a point this stops being true. Instead, the value of what you create becomes more important. You create this value in smaller moments, and you create far more value in this shorter period of time. The rest of your time is training for those moments.

The creative process isn’t magic - it is a rigorous process. For example, coming up with one great idea by brainstorming then filtering down those ideas.

1000 ideas –> 100 good ideas –> 10 very good ideas –> 1 great idea.

To perform this process, you need to make the brainstorming process as cheap as possible, so it doesn’t take too long to come up with the 1000 ideas. The number 1000 here was used literally, so you actually have a list of 1000 ideas before you start to filter them down. If you have less than 1000 ideas to start with, you’ll have less chance of having found the 1 great idea. This process relies on trust, so that everyone present feels comfortable blurting out “stupid” ideas.

Be courageous - don’t do something just because “that’s what everyone else does”. We need to learn from failure, and to do that we need to talk about it.

A classic question - “What would I try if I knew I could not fail?” but this question seemed to be opening up more possibilities for me. Very interesting if you can really look at answering it deeply.

Two techniques for meetings:

  1. You come to a meeting with a problem that you need help with. You state your problem, but before anyone is allowed to answer, everyone has a chance to ask questions (and only questions) to clarify what was meant by the problem. This avoids people getting stuck on the first solution that comes to mind, which is often formed on an incorrect understanding of the problem.
  2. Once people are ready to answer, face away from them and write notes. You are not allowed to talk. This way your own point of view (which hasn’t been able to solve the problem for you) won’t influence them, and they’ll be able to freely discuss a solution.