lukethomas

7 ms·

1.
by lukethomas 4y ago
I didn't want to fleece future investors or existing/future employees. When running a startup, it's natural to have unknowns, and for the most part, that's okay and to be expected. But if you discover a new reality on th
2.
by lukethomas 4y ago
We raised a total of $2.6m, so nothing too crazy in today's market.
3.
by lukethomas 4y ago
This was precisely our approach, but we built our own features for the "gaps" that we believed existed in the other products. If an existing app was doing a decent job, we didn't want to compete with them. The issue is that w
4.
by lukethomas 4y ago
Absolutely. I will 100% keep this up and running and freely available for all. It may be on my own personal website though.
5.
by lukethomas 4y ago
I bootstrapped the company for years before raising. I raised because I felt that I had to go after the bigger vision, which required resources ($$). In short, I wanted to accelerate the pace of learning, because if I didn't, I would a
6.
by lukethomas 4y ago
Heck no. If we were profitable, I would have kept it up and running and reduced things to a skeleton crew.
7.
by lukethomas 4y ago
I knew we needed to build a suite of tooling, as our goal was to be a "hub" for the most important stuff at work. In retrospect, we built too much product. If I start another company, I will spend all my time focused on solving a
8.
by lukethomas 4y ago
I originally called it "Friday Feedback" - you will probably see a launch post ~6 years ago with a search for that :)
9.
by lukethomas 4y ago
I made the decision after a lot of reflection. We still had ~6 months of runway so I could have spent more time "pivoting" around. The issue was that what I was hearing from prospects, customers, users signaled a bigger issue that
10.
by lukethomas 4y ago
I am considering it. I have a fiduciary duty to try to fetch a fair value for the assets, but if no one wants the codebase, I'd consider opening it up. Still TBD as I just announced this a couple days ago :)
11.
by lukethomas 4y ago
Hey, I'm the founder. We worked really hard to not position ourselves as a task management tool, but instead, a tool that integrates with existing systems. Task management is extremely competitive and we didn't want to play in the
12.
by lukethomas 4y ago
Thank you. Just trying to do the right thing given the circumstances.
13.
by lukethomas 4y ago
Hey there, I'm the founder. Happy to answer any questions people have. This was a decision I didn't take lightly.
14.
by lukethomas 5y ago
Hi HN! tl;dr - I wrote a 200 page user manual for team leaders and CEOs to navigate working from anywhere and open sourced it online for free: https://friday.app/anywhere I'm Luke, the founder of Friday.app. 8 years ag
15.
Show HN: I wrote a 200-page book on remote work (it's free)(friday.app)
2 points by lukethomas 5y ago|1 comments
16.
Slack Is Not Asynchronous(medium.com)
5 points by lukethomas 5y ago|1 comments
17.
How to create a wiki for your remote company(friday.app)
2 points by lukethomas 6y ago|0 comments
18.
Friday.app, a remote work tool, raises $2.1M led by Bessemer(techcrunch.com)
2 points by lukethomas 6y ago|0 comments
19.
Remote Work Mental Models(friday.app)
2 points by lukethomas 6y ago|0 comments
20.
by lukethomas 6y ago
async is not a losing battle. Trying to handle async communication processes manually is. Right now, most async communication processes (like status updates or daily standups) involve a ton of manual effort to make sure that people share th
21.
by lukethomas 6y ago
Most workplace communication tools are focused on improving the efficiency of communication. I think of this as laying "pipes". It's never been easier to jump on a video call or ping someone in Slack or email. What happens is
22.
by lukethomas 6y ago
Any wiki software suffers from the problem that only a small percentage of the company uses it. It's essentially a tax on the most productive people. If someone asks you for the same thing 8x, you will write it down and share it via a
23.
by lukethomas 6y ago
This is right on. Slack's pricing is based on regular usage, so they have an incentive to keep you distracted (to put it bluntly). Microsoft sees chat as a piece of an overall communication "puzzle". They have Sharepoint for
24.
by lukethomas 6y ago
My journaling habit started with Ohlife.com way back in 2014. I found the idea of quickly recapping my week to be therapeutic., plus it was great to see entries over time. I ended up building a product ( https://www.friday.app&#x2
25.
Routine meetings are (mostly) a waste of time(digg.com)
14 points by lukethomas 6y ago|1 comments
26.
by lukethomas 6y ago
This is awesome! I've really enjoy watching the interviews they publish on Youtube: https://www.youtube.com/channel/UCNc-Wa_ZNBAGzFkYbAHw9eg
27.
The future of remote work is flexible work(friday.app)
1 points by lukethomas 6y ago|1 comments
28.
by lukethomas 6y ago
The solution to Zoom fatigue is to eliminate meetings where the purpose is to share basic facts & information. Save meetings for collaboration, relationship-building, and working on thorny problems.
29.
The remote work movement isn't about working remotely(digg.com)
1 points by lukethomas 6y ago|0 comments
30.
by lukethomas 6y ago
This is a great point. The issue is that the current best practice advice is to use a wiki. Wikis are riddled with problems. They become out of date quickly. They need a librarian over time to organize the content in a way that's meani

More ›