Please enable JavaScript.
Coggle requires JavaScript to display documents.
request quality (bad requests (traits) (bad process (just send us a list…
request quality
bad requests (traits)
examples of bad requests
Prepaid: big issue isnt CI, big issue is legal/regulatory. we know what we want to do, but what we offer is not going to solve the problem at all. Internal roadblocks are the real issue.
give us the strategic importance of this project or where we think the end result of this project is so we can craft the results to meet the request.
-
-
-
-
-
-
personal note: the "fun", interesting, requests are ones that we get to stretch our knowledge and feel like we are creating real value. Looking into new things, areas where people havnt looked yet, learnings something new, etc.
bad process
-
seem like they arent actually necessary, they are just thinkgs you might like in the future
no meeting, no further guidance in between request and deadline
good requests (traits)
-
-
-
-
examples of
good requests
speakman request
very involved, he pushed us to produce something valuable, we met a few times before deadline to ensure we were all on same page
portable power request
less thought provoking, but the initial request on pricing turned into a broader ask of what our opinions on the entire market were. What was our opinion of the broader business environment, and what recommendations might we have for ways to move forward. That aspect of the project was extremely valuable and fun for us. The googling of competitors prices was not. It was also fun to call people and talk to them briefly.
Good parts of Process
always better when Requester is involved and we iterate throughout the request. This helps for conversation as well as scope management and guiding the research in the exact way we want it to go to provide the most value.
-
-
-
-
good projects: CI and business are involved and working together to solve problems and create value. Stretching knowledge and limits.
-