User talk:Tonyc - Revision history

Tonyc: /* DB */

2008-10-30T18:26:07Z

Tonyc: /* DB */

2008-10-30T18:16:10Z

Tonyc: /* DB */

2008-10-29T03:15:24Z

Tonyc: /* DB */

2008-10-29T03:13:40Z

Tonyc: /* Ideas */

2008-10-29T03:13:04Z

Ideas

Tonyc: /* Ideas */

2008-10-29T02:55:37Z

Ideas

Tonyc: /* Challenges */

2008-10-29T02:31:25Z

Challenges

Tonyc: /* Impressions */

2008-10-29T02:23:50Z

Impressions

Tonyc: /* Impressions */

2008-10-29T01:38:52Z

Impressions

Tonyc: /* Impressions */

2008-10-29T01:17:53Z

Impressions

@@ Line 136: / Line 136: @@
 login cashier
-add small box at top of entry screen for a cashier to inital each xaction (or use any two digit code)
+add small box at top of sale entry screen for a cashier to inital each xaction (or use any two digit code)
-this will make it clear from a paper receipt, and in the database who entered every single transaction. Actually logging into the database each time is not feasible, this would be relatively simple solution
+this will make it clear from a paper receipt, and in the database who entered every single transaction. Truly logging into the database each time is not feasible, but requiring inits on each sale would provide better tracking and problem. It would also avoid the "so and so told me I could return it" conundrum. We know who helped who. this would be relatively simple thing to implement, I think. (We tried opening db with different log ins in different tabs, but it was not possible).

← Older revision		Revision as of 18:16, 30 October 2008
Line 133:		Line 133:

	then the small print"		then the small print"
		+
		+
		+	login cashier
		+	add small box at top of entry screen for a cashier to inital each xaction (or use any two digit code)
		+	this will make it clear from a paper receipt, and in the database who entered every single transaction. Actually logging into the database each time is not feasible, this would be relatively simple solution

@@ Line 118: / Line 118: @@
 ==== DB ====
-update category list. currently not intuitive or complete. Make more intuitive for training (CRT and LCD become "Monitor--CRT" and "Monitor--LCD." Some categories missing, such as "motherboard," especially on expensive items having detailed receipts is going to make returns easier to handle and more difficult to abuse. Or changing "card" to "card, card--sound, card--video, card--misc., etc." For small items, or as-is items, card would suffice, but the option is there to use arrow keys to instantly add more info for things over a few bucks. Also can help us spot trends more easily and accurately by having more detail available..
+update category list. currently not intuitive or complete. Make more intuitive for training (CRT and LCD become "Monitor--CRT" and "Monitor--LCD." Some categories missing, such as "motherboard," especially on expensive items having detailed receipts is going to make returns easier to handle and more difficult to abuse. Or changing "card" to "card, card--sound, card--video, card--misc., etc." For small items, or as-is items, "card" would suffice, but the option would be there to use arrow keys to instantly add more info for things over a few bucks. Also can help us spot trends more easily and accurately by having more detail in categories. The less we use misc., the better.
 Notes

@@ Line 117: / Line 117: @@
 Any place else this model of physical example could be brought in will streamline training and make the experience of shopping easier and more inviting.
-== DB ==
+==== DB ====
 update category list. currently not intuitive or complete. Make more intuitive for training (CRT and LCD become "Monitor--CRT" and "Monitor--LCD." Some categories missing, such as "motherboard," especially on expensive items having detailed receipts is going to make returns easier to handle and more difficult to abuse. Or changing "card" to "card, card--sound, card--video, card--misc., etc." For small items, or as-is items, card would suffice, but the option is there to use arrow keys to instantly add more info for things over a few bucks. Also can help us spot trends more easily and accurately by having more detail available..

@@ Line 100: / Line 100: @@
 === Ideas ===
 Make Metro shelves currently interlocked into stand-alone, movable units.
 Vertical blinds to close at night--vertical and broad to make them less likely to get messed up. Able to be retraced by a pulley on one side, easy to operate.
 LED reader: blinds would mean LED reader would need to come down. What's the story with this? This would be an excellent way to make our store policies abundantly clear. Hang on back wall and program it to provide FAQs, especially with regard to return policy.
-Database:
+Policy signage and handouts.
 update category list. currently not intuitive or complete. Make more intuitive for training (CRT and LCD become "Monitor--CRT" and "Monitor--LCD." Some categories missing, such as "motherboard," especially on expensive items having detailed receipts is going to make returns easier to handle and more difficult to abuse. Or changing "card" to "card, card--sound, card--video, card--misc., etc." For small items, or as-is items, card would suffice, but the option is there to use arrow keys to instantly add more info for things over a few bucks. Also can help us spot trends more easily and accurately by having more detail available..
 Make easier to add notes. Notes field could always be visible, but tab order would skip over it, from gizmo to qnty to price. to add a note, click with mouse. Once you've opened the notes window, it throws of the rhythm of tabbing through the form for items that follow.

← Older revision		Revision as of 02:55, 29 October 2008
Line 99:		Line 99:

	=== Ideas ===		=== Ideas ===
		+
		+	Make Metro shelves currently interlocked into stand-alone, movable units.
		+	Vertical blinds to close at night--vertical and broad to make them less likely to get messed up. Able to be retraced by a pulley on one side, easy to operate.
		+	LED reader: blinds would mean LED reader would need to come down. What's the story with this? This would be an excellent way to make our store policies abundantly clear. Hang on back wall and program it to provide FAQs, especially with regard to return policy.
		+
		+	Database:
		+	update category list. currently not intuitive or complete. Make more intuitive for training (CRT and LCD become "Monitor--CRT" and "Monitor--LCD." Some categories missing, such as "motherboard," especially on expensive items having detailed receipts is going to make returns easier to handle and more difficult to abuse. Or changing "card" to "card, card--sound, card--video, card--misc., etc." For small items, or as-is items, card would suffice, but the option is there to use arrow keys to instantly add more info for things over a few bucks. Also can help us spot trends more easily and accurately by having more detail available..
		+
		+	Make easier to add notes. Notes field could always be visible, but tab order would skip over it, from gizmo to qnty to price. to add a note, click with mouse. Once you've opened the notes window, it throws of the rhythm of tabbing through the form for items that follow.
		+
		+	check boxes or drop down menu next to each item displaying "As-Is" "Tested--7days" and "System--30days." After items are entered, proper category assigned to each. Report could lump items into groups to better explain and communicate policies. RIght now it is so easy to peel off an as-is sticker. Many items are marked as "misc." or other unclear categories. Eliminating time-consuming and unpleasant exchanges with questionable returns. The receipt would still ahve the tiny print, but we could include plain english, clear and unmistakable language, so the receipt would appear:
		+
		+	"The following items are sold as-is and are inelligable for return:
		+	2 cables
		+	1 card
		+
		+	The following items are eligable for...blah blah
		+	1 card-video
		+
		+	then the small print"

@@ Line 49: / Line 49: @@
 By about 3 hrs into the first day, I felt like someone had slipped me something, or actually more like I had a concussion.
-Biggest challenge for me so far is swallowing ideas, as opposed to throwing them around. It makes sense and I don't disagree with it, but it's strangely painful. I think this has a lot to do with the fact most of my prior experience involves being involved in nascent projects, not well established ones with a history and culture to learn. I'm used to figuring things out from scratch.
+Ideas
 Jumping into the communication systems without fully understanding the culture that dictates their use is another rough spot. The Netiquette page is a handy place to start, but it's hard to dive in until I learn more of the nuance to how it's used. I need to get used to frequent and thorough checking of various places, signing up to watch pages, etc.
 Also, a talk early on about security, as in what info should go on what wiki, a reminder about using public terminals, would be useful. Mainly a debrief about rt and lists. This info came to me fairly soon, but here and there. Seems easy for a new hire to make a slip up in the first week, posting to the wrong place. Seems like a once paragraph summary of which places are considered "secure" and emphasizing that everyplace else is considered public.
 === Feedback on the process ===

@@ Line 17: / Line 17: @@
 I am not a flowchart kinda guy. You should know this about me. I can't really use them, and I have never made one. It is not the way I am wired, but it seems to be a large part of the culture here. Luckily I had Blaine there to show me the ropes, so I didn't have to use the charts too much.
-By the time I left, I was fully overloaded, and stayed that way all night, getting about one hour sleep (not an exaggeration). I think this is a physical response to learning so much at once; the energy required to form that many synapses in so little time is more than the system can handle. I laid there in bed and retraced the layout of the space, and saw people's faces, heard voices, saw the wiki. For the hour I actually slept, I dreamed about the frikkin' wiki! Disturbing. I think the full tour for closing procedure right at the end was what did me in.
+By the time I left, I was fully overloaded, and stayed that way all night, getting about one hour sleep (not an exaggeration). I think this is a physical response to learning so much at once; the energy required to form that many synapses in so little time is more than the system can handle. I think my brain got at least an oz. heavier. I laid there in bed and retraced the layout of the space, and saw people's faces, heard voices, saw the wiki. For the hour I actually slept, I dreamed about the frikkin' wiki! Disturbing. I think the full tour for closing procedure right at the end was what did me in.
 Day 2, Wed.
-Did not sleep the night before Went home in the afternoon. started off in prebuild, then working on cable sort
+Did not sleep the night before. Went home in the afternoon. started off in prebuild, then working on cable sort. Toward end of day, felt sudden need to flee. Luiz and Laurel, my two main contacts, were in a review (which I didn't know at the time).
 Day 3, Thurs.
 Attended action comm meeting. Luiz pulled me off the walk after we'd taken the field trip.
-met with laurel for a brief check in
+met with laurel for a brief check in. will type up notes from this day later.
 Day 4, Fri.
-Attended PR meeting
+Attended PR meeting. will type up notes from this day later.
 Day 5, Sat.
-Holy Shit
+Holy Shit. In the store from 10:30-7:30. Once customer interaction stood out above all others. will link to rt ticket on this one soon. "Learned" the till count-out. Finding discrepencies seems much more complicated than I'm used to, but having the db available looks insanely valuable. Just mind-numbingly complicated on first glance.

← Older revision		Revision as of 01:38, 29 October 2008
Line 82:		Line 82:

	Day 4, Tues		Day 4, Tues
		+	Learned of the Ombudsman today, and the policy of referring people who ask to talk to the "boss" to them. The one time this happened, the person eventually found this month's ombuds after I sent them to the front desk, but knowing such a position existed may have kept the situation from getting as charged as it did. I was almost sad to hear of this policy, because I had thought of printing this one really good picture of Bruce Sprinstein and mounting it to a board with a little bubble, "I'm listenin'" so I could pull it out in such situations and say, "Okay, here he is. Knock yourself out. Next!" (Just a fantasy, nothing I'd actually do).
		+
		+	Having the situation come up a lot where I know how to do something, like transfer a call, run a card, enter a sale, but for some reason it doesn't work. When I ask, the explanation is exactly what I thought I had just did, then there is the doubting look and raised eyebrow from whomever is helping me....When something doesn't work and I learn something it feels much better then when something doesn't work and I just can't understand why.
		+

	=== Challenges ===		=== Challenges ===

@@ Line 81: / Line 81: @@
 Day 3, Saturday
+Day 4, Tues
 === Challenges ===