plumshell

Work for only 3 hours a day, but everyday

I am an indie iPhone developer, and I’ve been working for 3 hours everyday for almost 2 years now. It may not work for everybody, but I started this habit in early 2014, and I have continued to do it since have I found that this is the most productive way to work for me.

Taleb and DHH advices

I first got this idea when I watched the talk by DHH (Rails creator) in the startup school.

He was saying this:

“Working long hours isn’t productive at all, if you work for 8 hours, try for 5 hours, or only for 4 hours. If you only have that time to work, you don’t have time to see Twitter while working.”

Also, when I read the book Antifragile by Taleb, he mentioned that the trick to working in a productive way over a long period of time is to only work for a short amount of time every day.

Making money on the App Store is really tough, and people don’t care how many hours I spend on my apps. They only care if it is useful or not. This is a completely result oriented world, but personally, I like it.

I have always thought about how I can optimize my time to work effectively, and after I tried a lot of different ways, I found it best to limit my work time each session for the best result in the long run.

Spaces are a very important factor in UI design, and that theory holds true for working.

Why 40 hours a week didn’t work

I can choose how I spend my time since I am making my own apps, so first I’d been searching for the most effective way to divide my work time weekly and monthly.

There is no one who orders me to work, and I can rest anytime, so I made a quota first. For example, my first quota was 40 hours a week.

I calculated my work time using a stopwatch, and I checked like “Ah, I worked for hours today”, and “I went out yesterday, so I couldn’t work, so let’s work more today”.

However, even if I work for the same amount of hours, the productivity depends on the conditions for each day. When I am tired or in a bad environment, I can’t focus. The work quality was not consistent at all.

Often, even if I could focus for the first few hours, the more time would go on, the less I could focus.

Work short hours every day

Then, I made a rule to work only 3 hours every day without holidays. This is a bit extreme, but in this short hour limit, you are more motivated to work harder to make your working time meaningful.

First, the most productive time for me is after I wake up, so I need to sleep well, and start working right after I wake up. I don’t read any news or SNS because even if I only read them a little bit, it could affect my productivity because it distracts my mind.

I even disable all notifications on my iPhone before I go to bed, so I don’t see them before I start working next day.

I prepare for each day seriously like an athlete who prepares for their games in the morning. There was a huge difference of productivity between a 9 hour work day and a 3 hour day.

You really think about what to do

This was a good discovery. When you have only a short amount of time, you care about what you do more than ever.

When I develop features on my apps, I think more seriously if I should do it. Is it really worth my time for today? Is this project worth doing?

I cared about it before, but the seriousness increases when you have only a few hours to work a day.

Less stuck for coding

When you are coding, you get stuck quite often, and it can take a lot of hours to solve it sometimes. However, with my 3 hour work day, I find that this happens less since you can’t keep digging into the issue when you don’t have enough time anyway.

This way, you will be able to find the solution or come up with something the next day with a different viewpoint.

My challenge is that it is sometimes hard to go bed without solving some unknown issues, and you don’t want to stop coding in the middle of it.

Nevertheless, when you take a break from the issues, you can think like “Well, it was not worth taking so much my time anyway…” in a calm mind the next day.

What if when you are in the zone?

Another pain for this method is that you should stop working anyway even when you are in the zone.

I often feel like I want to continue working when I am in the zone for some work. But, if you extend your work time rule once, you will do it again, then the more you extend, the more your productivity will drop.

It’s a hard trade off.

If I work for only a week, working more should produce more results, but when I work for a full month, the results from shorter work days will be more productive than if I was working longer days.

If I work for a year, I can complete my jobs more efficiently with this routine. I am sure I won’t retire after several years anyway.

Keep working until I die

Previously, I thought I would rather retire early and spend my life by having a fun without working at all.

With this method, I don’t get stressed so much even if I keep working years, so I thought I could keep working with fun until I die. This is the another surprising discovery I didn’t imagine before.

To stop working when I want to work more every day was the best way to keep working over a long period of time. It might fit me to keep running like a marathon runner with a same pace instead of working hard and retire early.

FAQ

I got a lot of mails after I posted this post, so I answer some popular questions here.

Q: I was wondering how work other than coding fits that profile. e.g. work with designer to prepare logo or any kind of promoting – that must be a part of your work as well, right?

Yes, I have to do everything, including UI&UX design, marketing, supporting and so on, since I’m a solo person. The coding might be around 50% of the work time.

Q: How do you monetize?

Free to use and In-App-Purchase for upgrading for Taxnote, Voicepaper, and Lisgo. ListTimer and Zeny are mostly ads based.

Q: Do you freelance, or are you available for hiring?

Not at the moment.

Q: What do you do with the remaining time?

I like reading and walking.

Q: Does it work for a freelancer?

Honestly, I don’t know, since I don’t have enough experience for that. I believe the best way to work depends on situations and preferences for each person.

I might change my habit completely in the future, if I come up with a brilliant startup idea, and want to work very hard on that every day.

I believe everyone has the right to choose how you use your time for the rest of your life. I consistently think about it too.

You can check interesting debates on HackerNews too!


*I make Taxnote and simple apps.




Meeting with Parse advocate Eric in Japan

The other day, I went to Facebook Japan office to meet Parse advocate Eric Nakagawa with my friend Kato.

From left, me, Eric, Kato.

We talked about Parse generally, but also talked about how they can grow their community here, so this article might be help for people thinking about growing their developer communities in Japan.

Last month, I visited Silicon Valley for the first time with Kato, and we had a dinner with George who is Kato’s former colleague.

George kindly introduced Eric to us after he heard we both use Parse and had a casual Parse developer meeting in Japan recently.

After we came back to Tokyo, we visited Facebook Japan office located in a fancy building called Ark Hills Mori Building in Roppongi. (Facebook Bought Parse two years ago)

The Mori building is the one of the most expensive office in Tokyo, it seems Facebook has a ton of cash in their pocket.

Facebook Japan Office

Eric’s Passion

He showed their office to us, and we went outside for lunch. The one thing struck me most is his passion about Parse. I felt he is an ideal person for the job, I could see he’s been thinking about how he can support Parse community deeply.

He talked like machine-gun about Parse and developer community, we could see his energy for the product easily. If you feel passion from someone, you will become to want to support it.

During our talk, we learned he’s been using Parse as a user for a long time, even before he joins Parse. He said he still plays with it for his own small project.

He said he loves this service, and with service like this, it’s no longer a dream for a small team with only one designer and one engineer to make a scalable startup in the near future.

This is exactly the same thing I felt when I tried Parse a few years ago. I believe even one person can make a scalable product in the future.

That’s why I wrote about it on my Japanese blog several times, and I’ve been using Parse for Lisgo, and my new app too.

Anyhow, I was impressed with his passion about Parse, so during our talk, I was thinking about how they can grow their community in Japan by taking a memo with JetDo to suggest my opinions later.

How to reach to Japanese community

For Japanese developers, it feels some distance from services from other countries like Parse.

That is because we are not good at communicating in English, so people usually feel a little uneasy about using them.

Of course, many Japanese use AWS and other services, but people start using them when they can find lots of Japanese resources for that in the Blog, Tech Magazines, and programming books.

Speaking of Parse, it handles database and it’s difficult to switch after you release your app with it. With mobile apps, you also need to let users install new versions when you switch backend.

I also felt anxious about using it on my app on the App Store first, because there were not enough resources on the web from other developers actually tried it.

Therefore, it’s really important to know that developer advocates like Eric exist for the community.

During our talk, I thought, even if you don’t know him in person, acknowledging his presence in Parse and his “Ask me anything” passion makes a huge difference for Japanese wondering if they should use it or not on their products.

Then, how do you accomplish that in scalable or cost effective ways in Japan? I thought about it for Parse first, but these suggestions could apply to other developer tools.

Show up at Tech events

This might be the first thing you come up with.

Fortunately, there are a lot of developers Meetups every week in Japan, so showing up and explaining Parse tips are basic things. Also, meeting developers in person is something which makes people feel closer to your products.

You can also give some incentive to developers who write blog articles about the talk in Japanese later, since the more developers write about products, the more people tend to try it.

After I suggested this first approach, Eric said something like this.

“It’s a nice idea, but I’ve seen that many people talk about their products in tech events, then go back to their home right away. I feel that is like a marketing, so I’d like to do something which can support the community well when I do something like that.”

I thought this is an opinion from a person who has experience in developing community, and think about it well, nice.

Hire Japanese advocate?

It’s difficult to find an appropriate one, so this is not the easy way, but the most effective way obviously.

One good example is Katsumi Kishikawa who joined the mobile database startup Realm recently.

He is a well known developer in the Japanese iOS developer community thanks to his contributions to open source and community.

I believe his presence in Realm has made a huge impact for other Japanese iOS developers, and many people have started thinking about trying Realm. I feel there are lots of Meetups about Realm and see more blogs about it since his joining.

It used to be a product from a startup overseas, but now, you can contact with a person you know in Japan, this difference is huge.

However, you can’t find a person who is very good at coding, and active in developer community easily like him, so I thought about other ideas too.

Show up in tech news sites

It depends on if good sites accept interviews or not, but it’s easier than other ways I suggest here.

During our lunch with Eric, I kept thinking in my mind like this, “Oh, if someone from tech sites could write about this talk, then a lot of Japanese developers can see his passion for his work.”

Japanese developers could feel close to your product by reading interviews with advocates, and you might be able to advertise office hours to developers when advocates visit to Japan.

Translating Helps, or another thing?

Translating takes time and costs a lot, even though the effect can be obvious. The issue is the balance between the cost and the merit.

So, maybe another way.

In Japan, people often buy a Japanese technical books to learn about new programming language and services at first.

For example, you can find lots of technical books written for people who want to start Amazon Web Service and Google App Engine in Japanese if you search on Amazon.co.jp.

This is because, official manuals are written in English in most cases, and reading that are not easy for us. Also, it always helps to read tutorial from different perspectives.

Usually, authors write these kind of tutorial books not for money, because royalties from the book itself doesn’t cover the cost for the energy of writing.

The authors would rather expect selling their personal or company names which could connect to their next jobs by writing technical books.

I believe encouraging and supporting developers who are thinking about writing tutorial books for your service at all cost is important especially in Japan.

Add to that, I personally requested that Parse will write a detailed help for migrating to another service like Amazon Web Service.

It’s true that most services fail before they need to worry about scaling and migrating, but it’s also true that people dream and worry about scaling before start using Mobile backend.

There are not so many articles about this topic on the web, so I guess some people choose AWS or their own server from the start to avoid migrating risks.

We might not need to migrate at all anyway in the future with Parse, but understanding the method of migrating to other services well could make it easy for people to start using Parse.

Ask Parse Anything.


*I make Taxnote and simple apps.




Start from the riskiest part

When I make new apps, I always try to check to see what is the riskiest part of the business.

Plus, I try to look for the fastest way to check that. I think like this for everything, including ideas for new apps, programming, and so on.

So, what is the riskiest part for me?

Motivation Risk

Motivation is the engine for everything. I believe this is the most important aspect of your work. If you lose it, it’s over. It is always reflected in your work.

Therefore, what I care about first is not losing my motivation during developments.

If I make something, I want to make something amazing. If I want to make something amazing, I need to keep going day by day. If I want to keep going, I need to pick something I can keep my passion for.

How is that measured?

My trick is to wait. I usually wait for weeks, even if I come up with something I am excited about.

When you get a new idea, you always get excited most at first, but after several days, that excitement could fade away gradually.

If you still have a passion for your new idea after a few weeks, it could be something that you wouldn’t give up on easily.

Technical Risk

Another important thing is to consider whether or not your idea is even possible to achieve with current technology.

You can’t create it if technology and ecosystem are not ready, no matter how much you want to make it.

This is also essential when I start programming something new. I always start from the hardest part, in other words, I want to start on the part of the project that I am not even sure that is possible to implement yet.

This doesn’t mean you must jump on the hardest thing at first, it means you find the most important thing and start from there.

It’s better to tackle on the most important and uncertain parts first, and skip the small things that you can predict.

It might feel good if you start from easy things you can do since you feel productive after seeing your progress. However, if you find out that the most important part of your app is technically impossible later, everything you did beforehand will be a waste of your time.

Demand Risk

This is the most difficult part to check.

The two things above are something you can see by yourself, but demand is different.

The only way to check this is to ship your product. Shipping takes time, that’s why you should start from the riskiest parts to minimize the risks.

There are tons of uncertain things in this world, including your health, environments, change of the ecosystem, and some things you never imagine.

So, skip the easy and small parts of your project, and start from riskiest things in easy and fast ways.


*I make Taxnote and simple apps.




Making a simple video tutorial is one of the most cost-effective ways for your apps

It is now the era of video. You see lots of promotional videos from dozens of new startups. Twitter co-founder Jack Dorsey also said “Don’t let users read, let them watch” when creating promotional sites.

I can intuitively tell this is the right approach. Nowadays, when I research something new, I hesitate to read descriptions of new things first. I’d rather search for video explanations or tutorials to get the summary of them before I read.

Even when I learn new programming languages or frameworks, watching video tutorials on YouTube helps me understand the basics much faster than reading documents at the beginner stage. The same goes for new users on your apps.

Even if you create decent descriptions and screenshots for your apps, they cannot win against video tutorials, which clearly show where you should tap and swipe with animations. There is a huge gap in usefulness between the two.

Making a good video is not easy

Having said that, it takes time to make a decent movie, especially if you want to make a really nice and professional video.

You should care a great deal about scripts, sounds, and editing. These things can cost a lot and take up a lot your time.

That’s why I didn’t place much of a priority on making promotional and tutorial videos, especially as an indie developer who didn’t have enough of a budget.

For example, you will see many high quality movies for apps like this on the web.

Making a video like this must have been expensive, and I certainly can’t afford it.

If you are running a startup, a video has an important role when you do fund raisings. For me, it’s enough if users can understand what it is.

For new users, I wanted to create a video that shows the experience they can get from the app, instead of just explaining how to use it.

Creating a video that demonstrates the user experience

It’s hard to make a video that really demonstrates the user experience. You certainly can’t make a good one within a few hours.

I made just such a video for my app Voicepaper.

It’s not quite as nice as the path video, but I guess it’s ok, considering I recorded it with my iPad. Thinking about scripts, recording, and editing with iMovie still took a lot of time.

If making a detailed video takes up too much your time and it’s not an easy task, I would prioritize and do other important tasks first.

Regarding the Voicepaper video, I still don’t know if making it was worth my time or not. Measuring the cost-performance precisely also doesn’t seem to be worth the time.

I was very lucky, just like getting a gift from Santa Claus. My competitor made my app promo video for free, but that kind of thing doesn’t usually happen.

Recording simple app usage tips is another option

The thing is, I thought making videos was not cost-effective enough before, but I was wrong.

From a developer’s point of view, I’ve always wanted to create very good ones, which doesn’t make my apps cheap.

But from the user’s point of view, they just want to decide if an app is worth downloading by looking at a quick video explanation.

Especially if you make tool apps like I do, users know what your apps are made for from the start. Therefore, showing them some basics on how to use the app could be enough.

You can also explain the benefits of your app briefly at the beginning of the video.

I realized this when I was learning a new programming language on YouTube.

You can learn quickly from documents or blog articles once you know the basics and backgrounds, but at the beginner level, watching easy tutorials is very effective and fast.

For example, if you are interested in making iPhone apps, here it is.

This is a video with only screen and voice, but it contains very detailed information that simple text with screenshots cannot cover. You don’t need fancy sounds, actors, and the camera even has shake correction.

This is it, I thought. Why I didn’t use this format before?

It doesn’t take very much of my time, probably only a few hours, including editing with iMovie. The cost of making it is very low, but it still makes a huge difference.

When I get questions from users, I try to explain how to use my apps in details without any technical jargon, which can be difficult. If I make a tutorial video once, the support process becomes easier since I can now just show the video and give brief explanations when needed.

I made one video in less than 3 hours

I started recording the usage of my bookkeeping app Taxnote.

0:10~ Basic Entry
0:55~ Add memos
1:15~ Editting entries
1:30~ Overview for entries
3:00~ Reorder categories
3:10~ Rename categories
4:15~ Bulk delete
4:33~ Data export
5:25~ Print your data
6:20~ About upgrading

English is not my native language and I don’t speak it fluently, but I can still show where to tap, swipe, and explain basic uses with my left hand.

All I did was record my explanations one by one with iPad, and then edit them with iMovie.

Speaking of editing, I merged several clips (4-5 minutes each) and added subtitles. In the end, I increased the speed of the video to 140% for users to watch it faster.

It’s that easy. It didn’t even take me 3 hours to finish.

I put this video on the top of the Help page with the table of the contents.

I always try to think of ways to get good results with a minimum amount of time, and this video tutorial is something I should have done earlier.


*I make Taxnote and simple apps.




Why Nintendo doesn’t release Mario on the App Store

Recently, I read an interview with Nintendo’s CEO Satoru Iwata on the Japanese gaming website 4gamer (Japanese only), which was very entertaining and interesting.

There are lots of interesting facts that I wasn’t aware of previously in the article, including that Satoru Iwata himself has a hard-core programing background and he actually was writing codes until he was 40 years old.

However, myself as an indie iOS developer making a living on the App Store, the most interesting part was that he clearly explained why Nintendo doesn’t want to release Mario on the AppStore.

Maybe he mentioned that reason in some interviews before, but all articles I had seen so far were just opinions from writers about why Nintendo wouldn’t do that, or why Nintendo should.

He mentions in the interview that Apple doesn’t have any incentives to protect the values of their content, since the content for Apple products are simply used to attract people who want to buy smartphones.

Apple creates a platform (the App Store) to sell their smartphones, but Nintendo creates a platform (gaming hardware) to sell their games. There is a big difference between them he explains.

Nintendo’s worst nightmare is a future where the value of contents are getting lower and lower. He says they can sell a lot of games to more people if they release their titles at lower prices, but they’d rather protect the value of games instead.

It seems that protecting the value of games is the challenge that they’ve been trying to solve, and clearly something that they are struggling with.

I can totally understand this logic as an indie iOS developer even though I am selling tools, not games. I know how difficult it is to create your own business on the App Store because your basic option is to charge money at lower price once and keep updating for free.

The main revenue of Apple comes from selling devices, not from the App Store. Therefore, they have incentives to lower the price of apps on the App Store so that more people will pay a higher price for their smartphones.

This should be another reason why we, iOS developers shouldn’t be able to use auto-renewable subscriptions “easily” for SaaS apps and don’t have options like paid upgrade on the App Store.

In this interview, Satoru Iwata talks with Nobuo Kawakami who started the company Dowango which is the popular movie streaming service called “Niconico douga” in Japan. Nobuo Kawakami’s insight is always very unique and he is the reason why I got into this interview.

Nobuo Kawakami explains that if the company creating the platform, it doesn’t build and sell content for that platform, then that platform is generally not going to be good place for content providers because the company creating the platform doesn’t have the incentive to sell contents.

Nintendo’s platform is a better place for content providers because Nintendo also sells their own games, and they have incentives not to lower the price of their content. This can also be true in some ways for Apple as they sell Final Cut Pro and other software for the Mac, but they pretty much release all of their iOS apps for free now.

Nintendo makes their platform to sell games, but Apple and Google make their platform for different reasons.

In my opinion, if the company creating the platform doesn’t care about content providers, the value of the platform will decline eventually. At this moment, many app developers still want to make apps on the App Store, since so many people keep coming to this platform.

Apple can ignore the whining from developers since the App Store is the best place to do business for now, but I believe they could attract more developers who can create great things by improving their rules.

For example, the idea of changing 30% revenue charge rate based on developer sales is very interesting to me. Check out the blog article below.
An Open Letter to Tim Cook Regarding the App Store 70 / 30 Revenue Split

If they make improvements to the App Store in the interest of the content providers, maybe in the future they can attract Mario too? I have no idea, but I think it would be great if that happens.

-Thanks to Derek Lee for rewriting my English.


*I make Taxnote and simple apps.




I released the simplest app I’ve ever made on the App Store

I made a redicuralsy simple timer app.

I made it since I had wanted the app like this for a long. It’s free, search for “ListTimer” on the App Store.

Download ListTimer Here.

※The language of the video is Japanese, but the app supports English too.

This is the simplest app I have ever made, but I created it because I personally want to use it.

Why did I make an another timer app?

I use the default iOS timer app very often, almost everyday. For example, I use it for setting my work time.

In this case, it’s ok to set 3 or 4 hours one time a day. However, if I want to set 3 or 5 minute timer quickly when I cook or do something, it’s a pain.

First, the tapping area on iOS timer app is very small, and you need to select your desired time carefully using that hard-to-use drum roll UI.

I have many situations in which I want to set a timer, but to keep using the iOS default timer app makes me tired everyday, and I wanted to fix it.

How about other timer apps available on the Store?

OK, I tried lots of timer apps available on the App Store myself first. I thought I could find the one suits me easily.

I was wrong, I could find nice apps which have lots of features, or looks cool, and are customizable in different ways. But, All I wanted was a simple app where I can set times very easily and keep using in the long run.

I needed a timer app focused on the part of setting times and starting it quick.

So, I researched on timer apps available, and how I can improve it to make the one I love to use very often.

In the end, I found the easiest way to set times is setting the time list from 1 min to 90 min from the first, and scroll it to start one of them with one-tap.

Every list height should be big enough to tap it comfortable, cool, this suits me best! This is great, simple is best, less is more! I don’t need the other features!

I showed it to my friend, and he said “You can’t set 1:30?”, but I answered calmly just like a king, “This app doesn’t need that, that is because I don’t need it”.

Honestly, I thought I might need to make it possible to customize times, but I can think about it later if this app becomes popular enough.

Background behavior

One problem, third-party apps cannot play audio like iOS default timer app does. This is the same for all third-party timer apps.

I enable Silent mode almost always so this is the most important part for me. If you disable Silent mode, it plays audio with notifications in the background though.

Therefore, this app sends several local notifications in a row to let you know the timer is done.

Local notifications vibrate your device even in the silent mode and background status.

By the way, it doesn’t consume battery power since it schedules a timer locally. It also works offline.

About App Store Descriptions

I like to try new things as much as possible for learning. This time, I have done a different approach on the App Store. Instead of writing the app description normal way, I wrote why I made this app over there.

It could be less boring rather than listing features one by one, oh, wait, this app doesn’t have enough features to list anyway.

I was worried about being rejected from the Apple reviewing process as claiming it as a too simple app, but maybe the reviewer read the descriptions and understood the concept.

Please try it out if you are interested in using the fast one-tap timer app.

Download ListTimer on the App Store here.


*I make Taxnote and simple apps.




My competitor made my app promo video for free

Sometimes on the internet, I happen to meet cool guys. However, this time was exceptional.

Last month, I got a short message like this.

My brother and I had a company that built an iOS app similar (in functionality at least) to your app.

We haven’t had much traction and are planning on pulling it from the App store.

I’ve used your app, and it’s quite good.

That being said, I have put together some assets (media kit and video) that might be of use to you (just picture your app in the video instead of ours).

Let me know if this is something you’d be interested in and I could look at re-purposing the video and ‘story treatment’ for you.

I also plan to update our site (reedeo.com) to re-direct people to your app.

Best of luck.

Regards,
David

My app Lisgo is a listen later app for Pocket users, and their app’s concept is same.

Honestly speaking, since there are many text to speech apps now, I didn’t know reedeo until he sent me the message, but I could easily tell they made a really nice promo video to explain the benefits of the app.

This is the original video for reedeo.

When I made Lisgo, it was really tough to explain the concept of the app, since most people said “I’d rather read articles, since it’s faster”.

I knew it would be nice to make a promo video for that, but I didn’t do that since it would take a lot of time and efforts.

I replied with thank you very much message, and I sent the free promo code for Lisgo.

Even though their app has a very similar concept, I know it still takes a lot of time to edit the movie for Lisgo, I couldn’t believe his kindness at the time.

Several days later, I got a message from him again.

I finished making the updates to the video, I hope you like it and can use it; here is the link to it on Vimeo.

Best of luck with Lisgo.

And, this is the video he made for Lisgo.

You can tell he didn’t just change some parts of the original video, but added extra scenes to explain the some best parts of Lisgo here. It’s awesome.

I was so impressed with his geniality, so I thought I should update Lisgo’s landing page at least to use this nice promo video efficiently.

It didn’t take so much time since I could use some codes of voicepaper page.

This is the previous Lisgo landing page.

スクリーンショット 2013-12-16 18.25.23

This is the new landing page look for http://lisgo.org/. The video must stand out compared to the previous one.

スクリーンショット 2013-12-17 21.00.05

Again, thank you David and your friends for taking your times to make the video.


*I make Taxnote and simple apps.




How do you say No to users without annoying them?

It’s often said that you should listen to your users to improve your product. However, the reality is, it’s a really tough challenge, and I believe you need lots of practice and experience to do it well.

I still find it difficult to say NO to users, but I want to share my thoughts about this.

I feel bad about saying No to user requests

When I was watching the iPhone5s Apple video, Jonathan Ive said something like this.

We are as proud of the things we have said No to as the things we have done.

I believe this is really important thing for product design.

When your users request or suggest some ideas, usually, every one of them makes sense in their contexts, and I can understand why they want that in most cases.

However, if I execute every great idea, eventually, the product becomes messy one with lots of noises. It ends up being a product nobody wants by trying to make something everybody wants.

We should choose what to execute very carefully.

Having said that, even though I know the principle in my brain, when I get requests from users, it’s still hard to say No to them. Users like your product, and took their precious time to write something to you, but you have to say NO most of the times.

This is not easy.

When I read the 37 signals book “getting real”, I remember they say “It’s hard to say No, but you have to be good at it”.

As a Japanese person, we have a stereotype image about Americans that they are good at saying No. But, even if they think that is hard, for Japanese people who are really bad at it, it must be really tough challenge.

So, what can I do.

How do you reply?

So, how can I say No to users.

To people who took their time to give me feedbacks and requests, how can I reply? I always find it really hard.

For example, one person say like “I need this feature because..”, and you know that is useful, but you want to protect simplicity of your product.

Let’s say you explained like, “I understand the value of the feature, but I cannot make it since I need to add features which will be used for 80% of users at least.”

In this case, for users who requested the feature, it doesn’t matter if they are in the 80 % category or not, I might end up pissing them off by explaining to them with data.

I really want to say “I will do it in the near future!”, but making a promise about future plan is the last thing you want to do in product development.

You never know how your product goes, and you cannot avoid changing priorities of product often. If you make a promise, and turned out you couldn’t make it later, users would be upset.

Again, in the “getting real”, it is recommended to say “we’ll think about it” basically.

“Think about it”… this carried me back to my childhood when I was blaming Japanese politicians always saying “I’ll think about it” without promising anything. I now know why they needed to say in that way somehow.

Basically, I try not to promise anything to users, because I can never tell what I am going to do for my products in the future.

Even if I expect I would definitely implement one feature, I try not to say I am working on that.

However, I feel bad to say the same template sentences like a robot to users, so at least I try to understand why users request some features and explain my situations sometimes.

How do you say why?

It’s important to say “why” to understand the backgrounds of each requests well. Some people say we should repeat why, so we can dig into the needs behind the requests.

However, in the real world, it is easier said than done. Don’t you think you get tired if you are asked “why, why?” when you just request one feature?

In this case, I try to confirm reasons, just like, “you are requesting this feature, because you have this issue, am I right?”

I believe it’s less annoying to users instead of being asked with why, and of course, this attitude can minimize risks of implementing new features without knowing the real reasons behind feedbacks.

Priorities…

It sounds convincing when you say that “I cannot do that since I should protect simplicity of my product…”, but, it could not be a real reason for not doing something in many cases.

Sometimes, implementing some feature takes too much time, or I cannot see any corresponding benefit for the time. Especially when you are selling apps for a few dollars with one time purchase business model.

In this situation, it is much harder to explain this to users.

Having said that, it’s really worth listening to feedbacks from users as much as you can, since you can learn something you have never thought of. Even if you get opinions you expected, that means you are validating your hypothesis.

If you seek for feedbacks from nowhere, it’s gonna take a time to meet people which are your target users.

When they come to you and ask for something, this is a golden opportunity to learn a lot and get valuable insights.

Plus, you feel great when you see people who actually care about your product. This is why, I set a feedback box using Helpshift for Taxnote, Zeny, and other apps.

I understand you want to avoid getting support emails for apps when you stopped updating in the future, but, at least when you are working on that constantly, it’s worth putting a feedback box inside of your apps.

Related articles

This is a really good article related to this topic.
PRODUCT STRATEGY MEANS SAYING NO

“Avoid Setting Publicly Visible Deadlines” part of this article.
Running A Software Business On 5 Hours A Week

37 Signals Getting Real. One of the best in product development.
https://gettingreal.37signals.com/GR_arb.php

***
I got an email from Gergana of SANSMAGIC saying this issue resonated with her. Her book about how you can reply to customers includes very detailed tips on this topic, and she shares her own experiences in the real world.
http://sansmagi.cc/resources/


*I make Taxnote and simple apps.




Copyright © 2016 plumshell

Theme by Anders NorenUp ↑