Understanding the way I think or process..
Boy this first draft opened a can of worms on me today. But its not all a loss. Maybe I suck at taking feedback, I dont think so but maybe, I do suck at that. The more I think about it, the more I open doors to better understand how I think and process. Often my writing is viewed as being too wordy or too “cute”. Again this is not an intent. I can be overly wordy when I want to, but I never try to strive for cute ness. Scarastic maybe sure, but I dont see that as cute. Unless were talkin “dont be cute with me” which is a form of scarasticness. Ok so maybe thats what they meant.
I look at it like this. I could say:
The apple is simple.
Thats simple, to the point, clear, but leaves out any room for any clarification or possible notion that the apple is anything other than simple. Research never works like that. There arent simple answers. Users dont break down bad design into it “just sucks” theres aways a reason, and yer a bad researcher if you just accept “just sucks” as an answer cause thats really a permission to probe further for people. They are asking you to ask them to deep deeper. If they tell me:
The apple sucks cause its red, round has a shine to it, makes me feel simple, too possible, too easy, its simplisitc, its not where i want to be, i’m not just an apple.
I tend to write that out, thats a nice base to word. Meaning that the way I write is wordy cause I can work from words down, I cant work from simple up. If you have no data you have nothing to go on. But if you have data you can purify that to where you want to be. Does that make sense? Start large, refine to finish. Thats why I write gobs of material. You may clarify it later which is fine, I will clarify it later as well, but unless i understand where i’m at i can make the jump to clarity without the data present to help formulate it.
Do more of that in yer head. Well I cant.