Probably, I may try to do something different. Try to correct from what I learnt in past, but it's still kind of boring to go through same which we did in the past, so something new could help like exploring new ways of doing things and evaluating outcomes. It's a wild thought....
...
1 reply by Steven Zachary
Dec 26, 2015 3:38 PM
Steven Zachary
...
Boring for you, but not for someone else.
My intention with this thread was to try to discover people's greatest learning moment or "ah-ha!" moment when looking back as past performance. Call it a lessons learned if you will. The top lessons learned of all the lessons learned.
Saving Changes...
Steven ZacharyDirector| Alberta Health ServicesCalgary, Alberta, Canada
Dec 26, 2015 11:37 AM
Replying to Sandilyan Ramadoss
...
Probably, I may try to do something different. Try to correct from what I learnt in past, but it's still kind of boring to go through same which we did in the past, so something new could help like exploring new ways of doing things and evaluating outcomes. It's a wild thought....
Boring for you, but not for someone else.
My intention with this thread was to try to discover people's greatest learning moment or "ah-ha!" moment when looking back as past performance. Call it a lessons learned if you will. The top lessons learned of all the lessons learned.
...
1 reply by Sandilyan Ramadoss
Dec 27, 2015 2:01 AM
Sandilyan Ramadoss
...
True, I agree to your point. If you have to go through same set of incidents (moving back to the past time period), it might make you feel bored rather let’s call it as uninteresting or could even make you enthusiastic it depends on person to person and case to case... Further, we know that there’s always place for betterment in any projects, so we may run into risk of making the project go endlessly! just adding my thought in this.
In reality, it is we cannot spend more time doing R&D on what’s happened in the past unless it’s required for next step. Let’s try to avoid looking back, just keep moving, prevent those issues on what’s coming up next. What’s happened is already happened and is rework only, learn from it and proceed next.
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
I would tell a new BA that the key is influencing people: you don't need to know it all if you can get if from other people.
My intention with this thread was to try to discover people's greatest learning moment or "ah-ha!" moment when looking back as past performance. Call it a lessons learned if you will. The top lessons learned of all the lessons learned.
True, I agree to your point. If you have to go through same set of incidents (moving back to the past time period), it might make you feel bored rather let’s call it as uninteresting or could even make you enthusiastic it depends on person to person and case to case... Further, we know that there’s always place for betterment in any projects, so we may run into risk of making the project go endlessly! just adding my thought in this.
In reality, it is we cannot spend more time doing R&D on what’s happened in the past unless it’s required for next step. Let’s try to avoid looking back, just keep moving, prevent those issues on what’s coming up next. What’s happened is already happened and is rework only, learn from it and proceed next.
...
1 reply by Steven Zachary
Dec 27, 2015 2:29 AM
Steven Zachary
...
So, I take it you are against reuse then?
I think there is great waste in reinventing the wheel every time. If you don't have enough time to evaluate your work, which should have been done in the definition phase, then how will you know if you are truly successful. Further, how will you ever improve.
Being bored seems....well...trivial??
Saving Changes...
Steven ZacharyDirector| Alberta Health ServicesCalgary, Alberta, Canada
Dec 27, 2015 2:01 AM
Replying to Sandilyan Ramadoss
...
True, I agree to your point. If you have to go through same set of incidents (moving back to the past time period), it might make you feel bored rather let’s call it as uninteresting or could even make you enthusiastic it depends on person to person and case to case... Further, we know that there’s always place for betterment in any projects, so we may run into risk of making the project go endlessly! just adding my thought in this.
In reality, it is we cannot spend more time doing R&D on what’s happened in the past unless it’s required for next step. Let’s try to avoid looking back, just keep moving, prevent those issues on what’s coming up next. What’s happened is already happened and is rework only, learn from it and proceed next.
So, I take it you are against reuse then?
I think there is great waste in reinventing the wheel every time. If you don't have enough time to evaluate your work, which should have been done in the definition phase, then how will you know if you are truly successful. Further, how will you ever improve.
Being bored seems....well...trivial??
...
1 reply by Sandilyan Ramadoss
Dec 27, 2015 2:41 AM
Sandilyan Ramadoss
...
Steven, can you explain why you want to go back to the past? My stand point here is, we have learnt in course of time about our mistake (on-going). Why not we keep moving and use lessons learnt to prevent any further damages?
Community Champion
