Researcher Team (~2012.9.29)
Service Design Mini-Project Real Time
* Contact : http://bit.ly/PJzgjf
* Original! Proposal : http://bit.ly/PJA47Z
* Research team : Yuri Jung, Areum Kim, Jiyoung Gong, Eunjin Kwak, Pleasant Charles, Junpyo Park, Byunghoon Jung,
* ROLL : benchmarking, document organization, material management, interviews
* Schedule Week 1: why, how, what
Week 2: goals, proposal background + segmentation, eco-map, FGI
Week 5: FGI analysis
-----------------------------------------------------------------------------
0. [ Previously on the show ]
So it went. Last week, too, everyone — busy as they were — worked hard to exchange opinions both inside and outside KakaoTalk. Then, one Thursday evening, six of us including ChanwooChanwoo fatefully gathered at that very Sadang Station, which carries a certain man's sad story, and held a heated discussion. (For the past history, please refer to http://bit.ly/SO7D5E and http://bit.ly/UyIRMz.)
Conclusion. 1) As an internal opinion of the research team, decide the scope of "Real-Time."
2) lovers vs family vs personal network vs general relationships (unspecified many)
1. [ to-do ] Before the in-person meetup, ( This is homework ^^ think about it before the meetup ^^ )
1) <by Tuesday> By Tuesday, submit opinions on the scope of "Real-Time." (Please line up ^^)
* Lovers : Areum Yuri Yeonseon
Family : -
Network : -
General relationships : - Byunghoon Eunjin Charles
(This may be going a bit off-topic, but I think it could be fun even if it is not strictly person-to-person. Maybe like a feeling of saving & recording the precious time itself online? I am not saying to broaden the target, but I think it is good to leave the possibility open so it can be used in more diverse and fun ways.)
2. [ Other opinions welcome ^^ ] .
If anyone has been left out or something needs improving, please let us know or add items at any time~
1) How about this approach?
Just in case, I quietly asked our developer how much of the functionality is possible on iPhone too. On Android, without having to open the app or do anything special, you can use pre-set configurations to check and record within a range, but on iPhone, apparently you have to open the app every time. If we do build it, the gap between the two OS environments should not be too large so that more users can use it without restriction. Should we build it ignoring the technical aspects, or take those into account and match the two environments as much as possible, or overcome such restrictions as much as possible, or design the interaction to fit the existing environment — all of this seems like things we should think about. It is best to match development and design to good UX, but there are also cases where that is not possible.. I thought we should at least be aware of this in advance.
Wow!! Thank you so much T_T for going this far to look into it!!! Ah! I remember the ice cream from last time~ haha I will definitely buy it for you haha (I have a concert ticket booked for the next presentation so I will not be able to make it lol Let's call it even with that lol lol)Ohhoho ^^ Okie okie, got it~ haha
I also agree with this opinion! I am against restricting ideas by considering technology right from the planning stage. But I think we also need a perspective that thinks about very basic technologies like the above to some extent so that a realistic service can be built.
Sounds good!! Let us talk about this part at today's in-person meetup too ^^ haha
2) How about setting the scope of Real-Time like this?
First, the scope of Real-Time has been set to "general relationships."
But since each of the details has not yet been defined, and opinions have not yet been shared,
there is still plenty of room for improvement ^^
If you have a different opinion, please leave it here~ Take the challenge! It is not too late!!! @@ /
3. A warm-up for the in-person meetup,
Number one! 1) The scope of use for [Real-Time] is "general relationships."
2) Accordingly, come with thought on goals and the proposal background. -> Finalize at the in-person meetup ^^
3) For the target, decide the segmentation.
4) segmentation에 따른 interview content, and find answers for the related schedule and method of gathering.
Number two! 1) Research team overall schedule sharing and opinion gathering
2) Adjusting the schedule around the Chuseok holiday
Ah.. hold on a sec! 1) Our research team does not operate by majority rule!!
However, once something is decided, we will not reverse it.
So I hope everyone will share their opinions fully at the right time.
→ You have a different opinion about Real-Time? Objection! Objection!! ^^ Oho!
Then please write your content in section 2-2) above! As I said before, it is not too late!! @@ /
4. [ to-do ] In-person meetup,
1) Meetup : Cafe Retro (2nd floor)
Come out of Sadang Station Exit 6, walk just a bit past the "Tom N Toms" cafe, then come up —
Thursday 8:00 PM2) Participants re-check! Please edit and check!!!
-> 가요~ : 찰쓰, 유리, Yeonseon
-> 힘들 것 같아요.. : 지영, 병훈, Eunjin
3) Share additional opinions!! Ohhoho ^^ !!
(I looked at the 'Bill Improvement Project...pdf' file that Jack Park uploaded to Dropbox haha I think it would be good to apply it well, adjusted to our theme ^^ After all, this was an attempt at service design! haha Everyone of course thinks so too :-) This is my first attempt at service design itself ^^ let us all work hard together!!~~~~~~
But one sudden question — I am curious whether our topic itself fits well within the scope of service design...! lol Because I do not know well T_T I need to study more.)
Oho!! Sounds like a good opinion!~ ^^ Let us refer to this part and move forward together~ Ah, however... ^0^ /
The difference between a work process for improving an existing service and the process for a service being newly built — let us figure out together, carefully, as we go~ ^^ Oh~ this is going to be fun~ haha haha haha
