Transcribed from hand-written notes-
16 March:
I really need to get my students in long talks and planning
for additional training with other analysts on how they want/desire/need the software to do together!!!
Then they need to work together (and with us,) to craft ways
to make the optimal outcomes of the systems (again; together) to = reality.
“Success for Them”
We also need to have “my guys” think through the
issues associated with having others do portions of their work on the back-end.
(This is to say, what they lose having others without their expertise do some
of their background analysis).
We need to have them do a study (like we used
to) that will include how they plan to incorporate additional information and
coordinate among themselves to on procedures of how they will deal with various
system issues and anomalies.
Standardized ways to compose a LOG for their
important stuff
Using depth (others, through collaboration…) and history (knowledge
learned,) involving analysis- use what you know to exploit (learn from,) what
you do not know.
-
Creativity
-
Experimentation
-
Patience – sometimes a lot… a lot of patience
coupled with experimentation often yields ‘knowing’
-
Judgement
-
*Confidence + innate ‘gut’ decisions… these may
be the hardest to make – separate healthy-knowledge based decision-making from
ego-driven ‘well I just know’ perspective
Relaxation of what you think you know and acting upon it
& stress to gain knowledge by looking deeper at:
-
Why was this designed this way?
-
Why is what it’s ‘supposed’ to look like, not actually
what it looks like? (Not taking for granted ‘the norm’ and looking outside of
this)
-
How do I act upon what ‘it was designed to do’
or what ‘it looks like’ vs. what its purpose is supposed to symbolize?
Me (stuff for me to to work on):
1. Need to draft an email w/ list, assignments,
expectations, etc.
2. Survey edits
No comments:
Post a Comment