4. Financial outlook
• Collected $105k in July already (very good)
• $160k in outstanding invoices (this is a lot!)
• Current 52-week window: $1.3m
• Total revenue year-to-date: $820k
• Current plan for 2014: $2.5m — uh, totally off track
5. Features shipped
• Rewrote JIRA and Confluence integrations
• Rewrote Google Integration
• Reporting for review- and 360 overviews
• Usability improvements across the board
• Unfortunately, that’s about it. :( Lots of support-
related features, bugfixes, performance tuning.
8. Overarching goal: Joy
• Great people we enjoy working with
• Great product that we can be proud of
• Great customers for whom it’s a pleasure to work
• Smooth processes that help us stay sane
• Oh, and we need to make money
10. Organic Growth
• We are hiring and planning to grow
• Could be 18 people at end of 2014. 30 at EO 2015
• There was a bit of a slump recently: Hard to find
great developers, the competition is stiff
• But we do have the money to hire
11. Talent Crunch
• But we will not lower our expectations!
• It’s a complex product. Very little “easy work”
• Average people will make far more mistakes
• They have more questions, less great ideas, and
will create unmaintainable code
• They require need more process. Which is bad
for everyone
12. Risk with hiring
• I expect everyone to be great from the start
• And to get even better over time
• Risk: Employee may lose interest, focus or vision
alignment over time
• Great people may leave
• Average people will stay. Forever.
14. What will we build?
• Whatever is necessary to “help great companies
improve”
• As long as it has to do with feedback and skills
15. Main themes
• Functional improvements for each module
• Crosscutting: Usability, performance, scalability
• Integrations: Display external data inside SI,
expose our data via REST, and import users+SSO
• Beyond the desktop: Mobile application, browser
extension, responsive design
16. Roadmap: Reviews
• Multiple Reviewers per review
• Discussion-feature for shared commenting
• Angularisation so we can make it much more
interactive
17. Roadmap: Objectives
• Overview screen
• Objective alignment
• OKRs
• Improved team view
• Assign people to cycles
• Chronological view
18. Roadmap 360s
• Ratings into Production
• Nominate yourself
• Allow managers to run the process for their own
team
• Improved notifications
19. Roadmap Messages
• Total rewrite because it has become
unmaintainable. Make sortable, searchable etc
• More focused on core usecases like note-taking,
1:1 preparations, kudos
• split out discussing reviews and 360s and
objectives into a similar but different module
21. Mobile
• Ship first draft of iOS application, use it ourselves
• Then build the more advanced features: Update
objectives, trigger reminders, see basic statistics
• Start looking for Android developer in Q4
22. Usability
• Visual cycle overview
• Timeline view for the profile/dashboard
• Tutorial mode
• General navigation improvements
23. Ok, but in what order?
• It depends! Seriously, there is no master plan
• Customer agendas change. What’s important today
might be useless tomorrow
• Our capabilities change! Front-end dev leaves,
Backend developer joins: Suddenly the roadmap
ordering changes too
• We are opportunistic!
24. Planning-considerations
• Is a feature/improvement easy to build?
• Is it (going to be) used a lot?
• Does it complement/complete an existing feature?
• Do we have someone to build it?
• Does it help with usability?
• Does it make us prettier?
27. US company
• Still in the process of setting up US service
company
• Will allow us to employ people full time
• When we look for new staff in Q4, consider renting
office
28. Berlin office
• We will start looking for a new office once we hit 8-9
employees being in on average. Should be around
November.
• We are looking at immoscout etc every now and
then to get a good overview. But most offices are
soooo ugly it makes me want to cry
