So this week has had its up and its downs, but most of all it has been educational for me. This one is going to be a standard reflection for me. Writing only.
This week
There is no point in beating around the bush with regards to Rapid Ideation 2. It did not work out, and this was mostly because I over-scoped, I did not put enough thought in to it, I did not reach out enough, you know all the usual stuff you do when you think you know it already.
But none of this is negative because come the end I managed to understand and learn from it, and I found a really good solution to the initial problem I wanted to overcome.
So the initial problem was based around starting a project, it takes to long to set up the things I have done several times before and there is no reason to not re-use stuff.
The solution was to curate a project that I could just open, delete a load of stuff I did not need, keep the stuff I did need and start going for it.
The problem with this is that it is in the wrong direction. Rather that starting with everything and removing stuff, I need to start with nothing and add stuff.
So I have now worked out that I need to curate a library of asset packs and self authored packages that I can import in to a project when I begin in order to get basics set up.
Wish I knew this two weeks ago before I did all the work on my first thought process.
The Reflective Part
I needed to do this. I really needed to fail at this project in order to learn from it. Obviously I can spot the obvious mistakes I made. My research was not thorough enough, my time management was awful, my practical application was based around favouring jobs rather than doing them in the order required.
But I was arrogant going in to this so I thought I could do it the way I wanted rather than stick to the method that has been tried and tested.
A few weeks ago, through the lectures on the course, I was introduced to K. Anders Ericsson and his work in the psychological nature of expertise and human performance. I have become really interested in his hypothesis behind what makes an expert and how it is less to do with ability and more do to with practical application. As Ericsson (2007) himself says “To reach elite levels of performance, you need to constantly push yourself beyond your abilities and comfort level.”
I think this project has allowed me to do this, I tried to do something that I thought I could do with my eyes closed but actually what I have done is push myself to test my knowledge, and found it lacking, so now I must find out more.
Thankfully this is a process based problem rather than a skill based problem, I have the skills its just how I apply them in a better way in order to make me a better practitioner.
Next Weeks SMART Target
Read Peak: How all of us can achieve extraordinary things by Ericsson and Pool and write a review of my findings on this blog for next weeks reflections.
References
Ericsson, K., Prietula, M. and Cokely, E., 2007. The Making of an Expert. [online] Harvard Business Review. Available at: <https://hbr.org/2007/07/the-making-of-an-expert> [Accessed 30 July 2021].
Ericsson, A. and Pool, R., 2017. Peak: How all of us can achieve extraordinary things. 1st ed. Vintage.
Figures
Featured Image: Photo by Rita Morais on Unsplash
0 Comments