Last semester, I was working with several classmates on a design project that aimed to foster the documentation process for a group of high school students. These students were working in teams designing games or apps while did not have an existing documentation process.
When we were researching on the scope and context of the high school students' projects to better understand their needs, we got the chance to interview their mentor, John. In our discussion, he discussed some current practices of students documenting and the challenges that came along with it. For example, how can students document moments, such as taking photos or videos, without "breaking the creative flow?"
Sometimes certain technologies sound easy. Like a simple one-button that takes a photo of the room when anyone presses on it. However, John proposed a question:
Then who is supposed to be in control of it?
I couldn't forget about the discussion on this button for the longest time.
As a photography fanatic, I realized that I have this same one-button on my camera too: the shutter that takes one click to take one more photo. Being so effortless to take a photo, it also brings complexities: for one, by having more photos taken, it brings the challenge of managing a larger photo storage, spending longer time to saving photos (and potentially deleting some), and a lot more file management work. The questions, in this case, has become
How should I control the power of controling it?