Practical ways to type less, reply faster and keep your team consistent.
Sales best practices give a team shared principles that support productivity and revenue. Adopt four practices: a shared to-do system, data collection, clear communication, and a culture that supports staff.
Developer productivity is better measured by outcomes than lines of code. Consider seven creative measures, including closed tickets, deploys, documentation written, code reviews completed, and conversations with others.
Customer service training ideas help support teams keep customers at the center. Try ticket roulette, peer and manager reviews, company-wide support shifts, and new product training, plus resources to go further.
Great code documentation reduces development time and support requests over the long run. Find out what code documentation covers and see examples from Ruby on Rails, GoCardless, Stripe, and TextExpander.
Email subject lines for sales decide whether a prospect opens your message. Get 29 subject lines for cold sales emails, guidance on writing your own, a tip for getting opened, and a way to store your favorites.
Customer service books help support teams learn from world-class companies and experts. Browse 21 titles on customer service, building a great customer experience, and skills that help people succeed beyond support.
Testing a website for keyboard users starts with checking tab order. See why keyboard navigation matters for accessibility, how to test the order of focusable elements by hand, and how to automate tab order tests.
High quality bug reports give developers the details needed to fix issues fast. Use three steps: add instrumentation to your app, capture each user's browser setup, and ask targeted follow-up questions.
A strong sales follow-up email has three parts: personalization, a compelling offer, and an easy way to reply. See how each part works, how they fit together, and use a personalizable follow-up email template.
